This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/66804] Alignment issue caused by auto vectorization
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 08 Jul 2015 09:16:59 +0000
- Subject: [Bug tree-optimization/66804] Alignment issue caused by auto vectorization
- Auto-submitted: auto-generated
- References: <bug-66804-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66804
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
CCP computes this precisely:
Visiting PHI node: # PT = { D.1842 } (nonlocal, escaped)
p_3 = PHI <&MEM[(void *)&xxx + 2444B](2), p_4(3)>
Argument #0 (2 -> 4 executable)
&MEM[(void *)&xxx + 2444B] Value: CONSTANT &MEM[(void *)&xxx +
2444B]
Argument #1 (3 -> 4 executable)
p_4 Value: CONSTANT 0x0 (0x0ffffffffffffffff)
PHI node value: CONSTANT 0x0 (0x0ffffffffffffffff)
but we don't record the alignment (because it looks useless to know - it's
byte alignment). So the alignment on the access (invalid due to your use
of a bogus aligned type) prevails.