This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/37216] [cygming] Invalid alignment for SSE store to .comm data generated with -O3
- From: "sherpya at netfarm dot it" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Oct 2008 18:54:24 -0000
- Subject: [Bug target/37216] [cygming] Invalid alignment for SSE store to .comm data generated with -O3
- References: <bug-37216-16627@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #40 from sherpya at netfarm dot it 2008-10-06 18:54 -------
I mean that with -fno-common alignment works, even with non patched 4.2, my
question is due to the fact that it's not so clear for me what no-common does
and adding -fno-common what are side effects?
do using something like dummy or nops in bss section does something wrong?
at this point a forced alignment to 16 wouldn't be such a problem for the space
wasted, at least this can avoid problems with sse code (16 bytes) and 3dnow (8
bytes)
gcc may need to disable sse code on mingw/cygwin or at least avoid implicit
vectorizations
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37216