public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/51315] gcc 4.6.2 miscompilation with -ftree-sra (included in -O2) on Debian/sparc
Date: Tue, 29 Nov 2011 10:34:00 -0000	[thread overview]
Message-ID: <bug-51315-4-uVbTgIkmkb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51315-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51315

--- Comment #3 from Mikael Pettersson <mikpe at it dot uu.se> 2011-11-29 10:18:00 UTC ---
I suspect it's a dupe of PR50569 or PR50444.

(And if you hate alignment bugs like me you might also want to know about the
4.5-only PR46483.)


  parent reply	other threads:[~2011-11-29 10:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26 19:21 [Bug tree-optimization/51315] New: " jurij at wooyd dot org
2011-11-29  4:54 ` [Bug tree-optimization/51315] " jurij at wooyd dot org
2011-11-29  9:58 ` mikpe at it dot uu.se
2011-11-29 10:34 ` mikpe at it dot uu.se [this message]
2011-12-01  9:27 ` jurij at wooyd dot org
2011-12-03 18:37 ` mikpe at it dot uu.se
2011-12-04 18:21 ` [Bug tree-optimization/51315] [4.6 regression] unaligned memory accesses generated with -ftree-sra ebotcazou at gcc dot gnu.org
2011-12-06 14:17 ` [Bug tree-optimization/51315] [4.6/4.7 " rguenth at gcc dot gnu.org
2011-12-06 16:42 ` ebotcazou at gcc dot gnu.org
2011-12-07 11:38 ` rguenther at suse dot de
2011-12-08  9:11 ` ebotcazou at gcc dot gnu.org
2011-12-08  9:15 ` ebotcazou at gcc dot gnu.org
2011-12-08  9:26 ` ebotcazou at gcc dot gnu.org
2011-12-08 13:24 ` gjl at gcc dot gnu.org
2011-12-08 14:22 ` gjl at gcc dot gnu.org
2011-12-10 12:01 ` jurij at wooyd dot org
2011-12-10 12:10 ` ebotcazou at gcc dot gnu.org
2012-01-05 22:22 ` ebotcazou at gcc dot gnu.org
2012-01-05 22:25 ` ebotcazou at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-51315-4-uVbTgIkmkb@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).