* Harald van D??k <true...@gentoo.org> schrieb: > The compiler is not totally free to ignore the register keyword. Both > the C and the C++ standards require that the compiler complain when > taking the address of a register variable. Other compilers will issue a > hard error for it. Fixing the code to not declare the variable as > register would be the correct thing to do.
BTW: is the register keyword still so useful nowadays ? Shouldn't a modern (optimizing) compiler be clever enough to find out when it can use registers instead of RAM ? > Make sure you *understand* warnings, and then you can decide whether to > fix the code, if there is anything to fix, or to ignore. hmm, is there a (portable) way to prevent a specific warning in an specific place ? (some kind of #pragma ?) cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ ---------------------------------------------------------------------
