public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/49067] Internal Compiler Error with -O3
Date: Fri, 20 May 2011 10:21:00 -0000	[thread overview]
Message-ID: <bug-49067-4-blO91jnW26@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49067-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |4.5.2
      Known to fail|                            |4.5.3

--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-05-20 09:56:39 UTC ---
I can confirm

> /space/rguenther/install/gcc-4.5.3/bin/gcc -O3 -fno-strict-aliasing -S t.i
/home/fcf/blender-svn/blender/source/blender/editors/space_view3d/view3d_select.c:
In function 'view3d_circle_select_exec':
/home/fcf/blender-svn/blender/source/blender/editors/space_view3d/view3d_select.c:2235:12:
internal compiler error: in get_constraint_for_component_ref, at
tree-ssa-structalias.c:3035
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

which is a regression from 4.5.2.  So I suppose Ubuntu has backported
some patches.

Reducing.


  reply	other threads:[~2011-05-20 10:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 17:38 [Bug c/49067] New: " asalina at snet dot net
2011-05-20 10:21 ` rguenth at gcc dot gnu.org [this message]
2011-05-20 10:35 ` [Bug tree-optimization/49067] [4.5 Regression] " rguenth at gcc dot gnu.org
2011-05-20 18:48 ` [Bug c/49067] " asalina at snet dot net
2011-08-01 14:00 ` [Bug tree-optimization/49067] " rguenth at gcc dot gnu.org
2012-07-02 10:44 ` rguenth 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-49067-4-blO91jnW26@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).