public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/47190] [4.5 Regression] ICE: in function_and_variable_visibility, at ipa.c:934 with static weakref variable
Date: Wed, 26 Jan 2011 15:10:00 -0000 [thread overview]
Message-ID: <bug-47190-4-uY64HvfHwY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47190-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47190
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[4.5/4.6 Regression] ICE: |[4.5 Regression] ICE: in
|in |function_and_variable_visib
|function_and_variable_visib |ility, at ipa.c:934 with
|ility, at ipa.c:934 with |static weakref variable
|static weakref variable |
--- Comment #6 from Jan Hubicka <hubicka at gcc dot gnu.org> 2011-01-26 14:55:55 UTC ---
I am surprised that this ICEs at 4.5, too, since I was under impression that
the sanity check was introduced in 4.6 timeframe.
Anyway, backporting is easy, so I will commit it to 4.5 branch if it is
approved for so.
Removing 4.6 from regression list.
next prev parent reply other threads:[~2011-01-26 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 14:44 [Bug tree-optimization/47190] New: [4.5/4.6 " zsojka at seznam dot cz
2011-01-06 16:02 ` [Bug tree-optimization/47190] " hubicka at gcc dot gnu.org
2011-01-14 14:28 ` rguenth at gcc dot gnu.org
2011-01-19 20:53 ` jakub at gcc dot gnu.org
2011-01-22 16:24 ` hubicka at gcc dot gnu.org
2011-01-26 14:40 ` hubicka at gcc dot gnu.org
2011-01-26 14:56 ` hjl.tools at gmail dot com
2011-01-26 15:10 ` hubicka at gcc dot gnu.org [this message]
2011-02-02 18:03 ` [Bug tree-optimization/47190] [4.5 " dnovillo at gcc dot gnu.org
2011-04-28 15:27 ` rguenth at gcc dot gnu.org
2012-07-02 9:49 ` 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-47190-4-uY64HvfHwY@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).