https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64953
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2015-02-10
Ever confirmed|0 |1
--- Comment #11 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to manuel.reimer from comment #0)
> So "something" is wrong with the optimization.
Not necessarily. Your program may have a bug in it: many bugs are only shown
up by higher levels of optimization.
We don't have your hardware and we don't have the full code to your
application, so we aren't going to be able to help you debug this.
To take this any further you'll need to show us why you think the compiler has
mis-optimized your code. I think that's a more useful approach than trying to
identify the change in GCC that causes the code to fail.
