--- Comment #5 from info at hex-rays dot com 2009-11-24 11:02 ---
What is embarrassing is that the compiler does not issue at least a warning and
changes the alignment depending on some very obscure factor. I understand why
it happens but really do not like it.
If I add one more line
--- Comment #2 from info at hex-rays dot com 2009-11-24 00:12 ---
Created an attachment (id=19107)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19107&action=view)
sample files to reproduce the bug -- sorry for the previous attachment
compile with
g++ gcc_align_bug.cpp my
--- Comment #1 from info at hex-rays dot com 2009-11-24 00:11 ---
Created an attachment (id=19106)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19106&action=view)
sample files to reproduce the bug
compile it with
g++ gcc_align_bug.cpp myadd.cpp
--
http://gcc.
l
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: info at hex-rays dot com
GCC build triplet: 4.4.1 - 4.1.3 and probably other builds
GCC host triplet: x86-linux-elf
GCC target triplet: x86-linux-elf
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42158
