https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96304
Martin Liška changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96304
--- Comment #5 from D. Richard Hipp ---
((In reply to Martin Liška from comment #3)
> > But, are we violating aliasing rules here? What am I missing?
>
> Likely you are, but I must admit it's sometimes quite difficult to find that.
> From
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96304
--- Comment #4 from Richard Biener ---
(In reply to Martin Liška from comment #3)
> > But, are we violating aliasing rules here? What am I missing?
>
> Likely you are, but I must admit it's sometimes quite difficult to find that.
> From
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96304
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96304
--- Comment #2 from D. Richard Hipp ---
(In reply to Andrew Pinski from comment #1)
> Does -fno-strict-aliasing helps?
The problem goes away if I compile with -fno-strict-aliasing. I should have
thought to try that.
But, are we violating
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96304
--- Comment #1 from Andrew Pinski ---
Does -fno-strict-aliasing helps?
