Tomasz Francuz writes:
> Ok, I’ve studied a little bit gcc sources, I’ve found sections
> responsible for generating different register loading instructions,
> and indeed there is no information telling to the compiler how to load
> data
>> From FLASH. This is easy to correct, I suppose. But I h
As I can see in my first post I would like to modify gcc AVR backend to
support new feature – putting vtables into FLASH not SRAM. That’s why I
sent my message here.
Ok, I’ve studied a little bit gcc sources, I’ve found sections
responsible for generating different register loading instruction
Zoltán Kócsi writes:
> So it is indeed a valid compiler issue, not an incompetent user issue.
> Probably an improvement request would be the best.
Thanks for the details on the AVR.
The question of gcc vs. gcc-help is not one of compiler issues
vs. incompetent user issues. Many highly competen
> This question would be more appropriate for the mailing list
> gcc-h...@gcc.gnu.org than for g...@gcc.gnu.org. Please take any
> followups to gcc-help. Thanks.
>
> Virtual tables will normally be placed in the .rodata section which
> holds read-only data. All you should need to do it arrange
2009/6/16 Ian Lance Taylor :
> Tomasz Francuz writes:
>
>> I would like to change gcc so AVR C++ port will use FLASH memory
>> instead of SRAM to store virtual function pointers. Does anyone try to
>> do it? I have no experience as gcc developer, so can you head me to
>> appropriate files/literatu
Tomasz Francuz writes:
> I would like to change gcc so AVR C++ port will use FLASH memory
> instead of SRAM to store virtual function pointers. Does anyone try to
> do it? I have no experience as gcc developer, so can you head me to
> appropriate files/literature about this particular problem?
T
I would like to change gcc so AVR C++ port will use FLASH memory instead
of SRAM to store virtual function pointers. Does anyone try to do it? I
have no experience as gcc developer, so can you head me to appropriate
files/literature about this particular problem?
TIA.
