public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47564] [4.6 Regression] internal compiler error in memory_address_addr_space, at explow.c:504
Date: Wed, 02 Feb 2011 10:00:00 -0000 [thread overview]
Message-ID: <bug-47564-4-LnZLGYNLh2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47564-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47564
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org
|gnu.org |
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-02-02 10:00:11 UTC ---
Created attachment 23211
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23211
gcc46-pr47564.patch
Updated fix. For 4.7 I'd say we want to split this reinitialization up, into
reinitializations that matter for tree optimizations (ideally those could be
saved into (and restored from) some save area pointed to from
TARGET_OPTION_NODE, e.g. init_set_costs can be saved into target_cfgloop
structure), and initializations that only matter from expand_gimple_cfg entry
till free_after_compilation (there we could remember the last
TARGET_OPTION_NODE (or global) and if current TARGET_OPTION_NODE (or global) is
different from it, call the init_* calls at the beginning of expand_gimple_cfg.
next prev parent reply other threads:[~2011-02-02 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 3:09 [Bug middle-end/47564] New: " dnovillo at gcc dot gnu.org
2011-02-01 3:10 ` [Bug middle-end/47564] " dnovillo at gcc dot gnu.org
2011-02-01 3:48 ` law at redhat dot com
2011-02-01 8:20 ` [Bug target/47564] " jakub at gcc dot gnu.org
2011-02-01 11:50 ` rguenth at gcc dot gnu.org
2011-02-01 12:33 ` [Bug target/47564] [4.6 Regression] " jakub at gcc dot gnu.org
2011-02-01 14:19 ` jakub at gcc dot gnu.org
2011-02-01 14:41 ` jakub at gcc dot gnu.org
2011-02-01 15:47 ` jakub at gcc dot gnu.org
2011-02-02 10:00 ` jakub at gcc dot gnu.org [this message]
2011-02-03 8:29 ` jakub at gcc dot gnu.org
2011-02-03 8:33 ` jakub 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-47564-4-LnZLGYNLh2@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).