C++ objects with virtual tables in eeprom

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello all:

I am wondering if anyone has ever implemented a __attribute__ or #pragma
statement for use with constructors to specify to the compiler that the
object does not exist in ram; therefore it can not just do a "MOV.L
<reg>,<memory>" with the register containing the virtual tables address.
The compiler I am presently using (from the chip vendor) does not take
into account that C++ objects that have virtual tables, might reside in
the eeprom. I am asking them to add this feature, and they are asking me
if there is a standard way of handling this. Any thoughts would be
greatly appreciated.

Thank you,
Jon


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux