This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/52571] vectorizer changes alignment of common symbols
- From: "mrs at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 09 Apr 2012 23:52:54 +0000
- Subject: [Bug tree-optimization/52571] vectorizer changes alignment of common symbols
- Auto-submitted: auto-generated
- References: <bug-52571-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52571
mrs@gcc.gnu.org <mrs at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mrs at gcc dot gnu.org
--- Comment #11 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> 2012-04-09 23:52:54 UTC ---
Ah, I had another thought. COMDAT and LINKONCE things I don't think can be
realigned for all the same reasons that one cannot align COMMON. I've not
thought about this long and hard, so, could be wrong, so, would be good to have
a C++ or a vectorizer person review the idea. The idea is, if you compile one
translation unit with a vectorizor on, and another with it off, we wind up with
two instantiations, each with different alignment, and the one picked at the
end need not be either of them, but rather an explicit instantiation. This
seems identical to what happens to common to me.