Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: aleksei.voity...@bell-sw.com
Target Milestone: ---
Created attachment 47212
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47212&action=edit
reduced testcase from the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92462
Aleksei Voitylov changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92462
--- Comment #5 from Aleksei Voitylov ---
(In reply to Richard Biener from comment #3)
> Indeed -fno-strict-aliasing might be a workaround (apart from the atomicity
> issue). Also using a character type for the access (uint8_t is _not_ a
> charac
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92462
--- Comment #9 from Aleksei Voitylov ---
(In reply to Alexander Monakov from comment #8)
> The full preprocessed source is provided and it clearly says
>
> typedef unsigned char uint8_t;
>
> in line 10, so it is in fact a character type.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92462
Aleksei Voitylov changed:
What|Removed |Added
Attachment #47212|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92462
Aleksei Voitylov changed:
What|Removed |Added
Attachment #47260|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92462
Aleksei Voitylov changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92462
--- Comment #17 from Aleksei Voitylov ---
(In reply to Andrew Pinski from comment #14)
> Have you tested gcc 7.5.0 that was just released? How about gcc 8.x? Have
> you tried that. There has been aliasing bugs in gcc before and this might
> alr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92462
--- Comment #25 from Aleksei Voitylov ---
(In reply to Richard Biener from comment #22)
> Fixed on trunk. Can arm people verify? I checked the DSE dump only. Bonus
> if you manage to create a testcase for the testsuite failing before, passing
