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 bootstrap/46856] [4.6 regression] internal compiler error in final_scan_insn breaks m68k-linux bootstrap
Date: Thu, 09 Dec 2010 23:48:00 -0000	[thread overview]
Message-ID: <bug-46856-4-VXubixUoaR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46856-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Mikael Pettersson <mikpe at it dot uu.se> 2010-12-09 23:48:36 UTC ---
A bisection identified r166371 as the trigger for this bug:

Author: jakub
Date: Fri Nov  5 19:00:27 2010
New Revision: 166371

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166371
Log:
    PR target/45670
    * expr.c (expand_expr_real_1) <case MEM_REF>: Use EXPAND_SUM
    instead of EXPAND_NORMAL for base expansion.

    * gcc.target/i386/pr45670.c: New test.

Reverting that change from gcc-4.6-20101204 prevents the ICE.


  parent reply	other threads:[~2010-12-09 23:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 23:19 [Bug bootstrap/46856] New: " mikpe at it dot uu.se
2010-12-08 23:22 ` [Bug bootstrap/46856] " mikpe at it dot uu.se
2010-12-09  0:05 ` rguenth at gcc dot gnu.org
2010-12-09 11:53 ` jakub at gcc dot gnu.org
2010-12-09 23:48 ` mikpe at it dot uu.se [this message]
2010-12-11 12:18 ` mikpe at it dot uu.se
2011-01-18  9:50 ` mikpe at it dot uu.se
2011-01-26 14:49 ` mikpe at it dot uu.se
2011-01-26 17:31 ` [Bug rtl-optimization/46856] " law at redhat dot com
2011-01-27  5:41 ` law at gcc dot gnu.org
2011-01-27  6:58 ` law at redhat dot com
2011-02-02 18:08 ` dnovillo 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-46856-4-VXubixUoaR@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).