--- Additional Comments From maarten at contemplated dot nl 2005-05-05
11:56 ---
(In reply to comment #2)
Reading your reply further, I understand that the behavior I observere is
correct and related to the fact that the 'int32_t' type is assumed to be
aligned.
It is not
--- Additional Comments From maarten at contemplated dot nl 2005-05-05
11:49 ---
(In reply to comment #2)
You are completely right, the code above merely demonstrates what happens when
one writes to an illegal address. The correct version,
*((int32_t *) &a.unaligned_int32) = 0x12
c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: maarten at contemplated dot nl
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: mipsel-netbsd2.0
GCC host triplet: mipsel-netbsd2.0
GCC target triplet: mipsel-netbsd2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21387
