https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117573
--- Comment #9 from Tarik Ibrahimović ---
(In reply to Andrew Pinski from comment #8)
> (In reply to Tarik Ibrahimović from comment #7)
> > Does "corrupted" mean it got mixed up somewhere in the compiling process? I
> > emphasize once again, tha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117573
--- Comment #7 from Tarik Ibrahimović ---
Does "corrupted" mean it got mixed up somewhere in the compiling process? I
emphasize once again, that the generated code does not cause any misalignments
when -O0 is used.
One more thing which may be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117573
--- Comment #6 from Tarik Ibrahimović ---
Does "corrupted" mean it got mixed up somewhere in the compiling process? I
emphasize once again, that the generated code does not cause any misalignments
when -O0 is used.
One more thing which may be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117573
--- Comment #4 from Tarik Ibrahimović ---
Hi,
I'm hereby providing a testcase for the reported bug.
The bug is that there is a full-word misaligned store to address 0x1517 when
compiler optimizations are used (-02 in specific). In case of no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117573
--- Comment #3 from Tarik Ibrahimović ---
Created attachment 59676
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59676&action=edit
Disassembly of the program
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117573
Tarik Ibrahimović changed:
What|Removed |Added
CC||tarik.ibrahimovic@chili-chi
