https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68601
--- Comment #8 from Keno Fischer ---
Great, thank you, I was having quite a bit of trouble trying to reduce this
one.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68601
Alexander Monakov changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68601
--- Comment #6 from Markus Trippelsdorf ---
I cannot reproduce the issue on Linux with latest gcc-5 branch.
Next week the gcc-5.3 release candidate should be available.
Many bugs were fixed since 5.2., so please check if this issue got fixed, to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68601
--- Comment #5 from Keno Fischer ---
Created attachment 36866
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36866&action=edit
Preprocessed source
Trying to attach again. This is part of latest LLVM trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68601
Markus Trippelsdorf changed:
What|Removed |Added
CC||trippels at gcc dot gnu.org
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68601
--- Comment #3 from Keno Fischer ---
`-fno-strict-aliasing` does not seem to change the generated assembly.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68601
--- Comment #2 from Keno Fischer ---
The default options used by LLVM's build system:
```
g++ -m64
-I/home/Administrator/julia/deps/build/llvm-svn/build_Release+Asserts/include
-I/home/Administrator/julia/deps/build/llvm-svn/build_Release+Assert
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68601
--- Comment #1 from Andrew Pinski ---
What options are you using? Can you try -fno-strict-aliasing? Some folks are
known to pay fast and lose with strict aliasing rules including LLVM
developers.
