This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/49413] over-optimization that causes valid code to segfault
- From: "gattis at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 4 Aug 2011 04:21:41 +0000
- Subject: [Bug tree-optimization/49413] over-optimization that causes valid code to segfault
- Auto-submitted: auto-generated
- References: <bug-49413-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49413
--- Comment #9 from Matt Gattis <gattis at gmail dot com> 2011-08-04 04:21:20 UTC ---
> However, on most archs I'm pretty sure the optimizer already checks alignment
> in order to do things like SIMD instructions. So this is probably a valid
> FEATURE REQUEST... that the optimizer supports (but not necc. optimize)
> pointers with arbitrary alignment.
The thing is, it works on every previous version of gcc I've tried, even with
-ftree-vectorize on, and works with 4.6 with every optimization except
-ftree-vectorize. I'm sure it breaks a lot of stable code. I was going to
just fix it myself and submit a patch, but the fact that it's even a question
whether or not this is a bug discourages me from spending time on it because I
know it'll just end up lost in some flame war. I've jumped off this sinking
ship anyway... code works fine on llvm/clang.