[Dune] [#674] strict-aliasing warnings with gcc-4.4

Dune flyspray at dune-project.org
Tue Jan 19 10:37:11 CET 2010


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#674 - strict-aliasing warnings with gcc-4.4
User who did this - Carsten Gräser (Carsten)

----------
Although some suggested solutions introduce a semantic change to iterators/enitypointers that would be better placed in 2.0 instead of 2.x I suggest to postpone this since there is no easy solution.

IMHO the best solution would be to
* clearly state '_must_ be compiled with -fno-strict-aliasing'
* note that 4.4 will produce wrong code without it but pre 4.4 gcc seemed to work fine
* automatically add -fno-strict-aliasing for gcc-4.x x>=4
* put this all this information also in a warning if compiled without -fno-strict-aliasing

----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=674#comment1651

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.




More information about the Dune mailing list