[Dune] [#493] test failure: dune-common/common/test/sllisttest

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#493 - test failure: dune-common/common/test/sllisttest
User who did this - Elias Pipping (pipping)

----------
If by line 51 you mean

  assert(alist.beforeHead_.next_);                                                                                                                                                                                                     

then no, I still get the failure.

The flags necessary to trigger the test failure are

  -O1 -fgcse -fschedule-insns -fstrict-aliasing -ftree-vrp

for me. It's possible to get a list of flags that are enabled w/ -O2 but not w/ -O1 this way:

pipping at bogus ~ $ diff -U0 <(g++ -c -Q -O1 --help=optimizers) <(g++ -c -Q -O2 --help=optimizers) | awk '/^+ / { printf "%s ", $2 } END { print "" }'
-falign-functions -falign-jumps -falign-labels -falign-loops -fcaller-saves -fcrossjumping -fcse-follow-jumps -fdelete-null-pointer-checks -fexpensive-optimizations -fforward-propagate -fgcse -finline-small-functions -fipa-cp -foptimize-register-move -foptimize-sibling-calls -fpeephole2 -fregmove -freorder-blocks -freorder-functions -frerun-cse-after-loop -fschedule-insns2 -fstrict-aliasing -fthread-jumps -ftree-builtin-call-dce -ftree-pre -ftree-vrp 
pipping at bogus ~ $
----------

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

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.