Wolfgang Denk wrote:
In message 48765849.5050306@freescale.com you wrote:
Wolfgang Denk wrote:
In message 921B6E79C3E18642BFFC1C8633C430DB01023B9A@CA1EXCLV07.adcorp.kla-tencor.com you wrote:
Try adding -fno-strict-aliasing
No, we don't want to hush up compiler warnings, we want to fix the problems instead.
It's not silencing a warning (if it were, it'd be a -W flag); it's disabling an incompatible optimization.
OK.
Then let me rephrase: We do not want to disable optimizations, ...
If you want to figure out what that code is doing and rewrite it to be compliant with strict aliasing, go ahead (I tried, and it made my brain hurt). In the meantime, we shouldn't be enabling the optimization on code that was written for an older version of the C language where such an optimization was prohibited, and where the compiler is letting us know that it thinks the code depends on the older semantics.
-Scott