Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
15 years ago

GCC 4.1.2 Issue. New toolchain soon?

I'm running into a bug where the following code causes a compiler error: class foo { public: virtual const char* name() const throw(); virtual const char* faux_name() const th...
Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
12 years ago

The functions are marled 'inline' as well.

However, even though they are static and only called once minor changes would stop the functions being inlined.

--- Quote Start ---

5a) I'd arranged for my nios data areas and the 'small io' to be within a 64k block (to get gp relative addressing for everything), but I'd missed a trick! I should have put the 'small io' below 0x7fff - then it could be accessed by offsets from r0. It would be nice if gcc supported such variables - probably need a gcc attribute (or a special section - attribute is probably cleaner).

--- Quote End ---

Actually I wonder if the linker could modify the instruction to use r0 instead of gp if the offset from gp is out of range but a valid offset from r0? There is a specific error message so there must be some specific code.