| 1 |
* Harald van D??k <truedfx@g.o> schrieb: |
| 2 |
|
| 3 |
> The compiler is not totally free to ignore the register keyword. Both |
| 4 |
> the C and the C++ standards require that the compiler complain when |
| 5 |
> taking the address of a register variable. Other compilers will issue a |
| 6 |
> hard error for it. Fixing the code to not declare the variable as |
| 7 |
> register would be the correct thing to do. |
| 8 |
|
| 9 |
BTW: is the register keyword still so useful nowadays ? |
| 10 |
Shouldn't a modern (optimizing) compiler be clever enough to |
| 11 |
find out when it can use registers instead of RAM ? |
| 12 |
|
| 13 |
> Make sure you *understand* warnings, and then you can decide whether to |
| 14 |
> fix the code, if there is anything to fix, or to ignore. |
| 15 |
|
| 16 |
hmm, is there a (portable) way to prevent a specific warning |
| 17 |
in an specific place ? (some kind of #pragma ?) |
| 18 |
|
| 19 |
|
| 20 |
cu |
| 21 |
-- |
| 22 |
--------------------------------------------------------------------- |
| 23 |
Enrico Weigelt == metux IT service - http://www.metux.de/ |
| 24 |
--------------------------------------------------------------------- |
| 25 |
Please visit the OpenSource QM Taskforce: |
| 26 |
http://wiki.metux.de/public/OpenSource_QM_Taskforce |
| 27 |
Patches / Fixes for a lot dozens of packages in dozens of versions: |
| 28 |
http://patches.metux.de/ |
| 29 |
--------------------------------------------------------------------- |
Archives