[Dune] [#805] test failure: test-oned

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#805 - test failure: test-oned
User who did this - Martin Nolte (nolte)

----------
>From the 2.0 release notes on the website:

Severe Bugs

Dune violates strict-aliasing
You have to compile DUNE will the the option "--no-strict-aliasing". Newer versions of g++ make more use of strict aliasing rules. If you don't use the "--no-strict-aliasing" option, you will receive many warnings, and you might even observe undesired results and unreproducible errors.

But we are not alone with this problem. Several software projects intentionally violate strict-aliasing. For example, Python 2.x did so to implement reference counting ( http://mail.python.org/pipermail/python-dev/2003-July/036898.html). The Linux kernel does this because strict aliasing causes problems with optimization of inlined code ( http://lkml.org/lkml/2003/2/26/158).

For more information see Flyspray task #674
----------

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

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.