public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bredelin at ucla dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/20521] ICE in cgraph.C with C++
Date: Sun, 20 Mar 2005 15:57:00 -0000	[thread overview]
Message-ID: <20050320155725.28185.qmail@sourceware.org> (raw)
In-Reply-To: <20050317202607.20521.bredelin@ucla.edu>


------- Additional Comments From bredelin at ucla dot edu  2005-03-20 15:57 -------
Subject: Re:  ICE in cgraph.C with C++

belyshev at depni dot sinp dot msu dot ru wrote:
> ------- Additional Comments From belyshev at depni dot sinp dot msu dot ru  2005-03-20 11:25 -------
> 
>>This is with today's (Mar 17, 2005) CVS, with Richard's Guenther's patch to
>>modify inlining heuristics.
> 
> 
> which one? please add references to all patches you installed or, better, try to
> reproduce ICE with clean tree by adding appropriate --param options.
> 
1. For now, I will just include the patch:

diff -r1.170 tree-inline.c
1249a1250
 >     case TARGET_EXPR:
1250a1252,1253
 >       if (DECL_P (x) && DECL_IGNORED_P (x))
 >       break;
1252d1254
<     case TARGET_EXPR:

2. However, it seems that as of Mar 18 CVS, the crash no longer occurs.
This is probably because of this change:

Fri Mar 18 10:00:16 2005 UTC  by hubicka
	PR middle-end/20225
	* cgraph.c (cgraph_mark_reachable_node): Assert that it is not called
	too late.
	* varasm.c (find_decl_and_mark_needed): Mark needed only when not
	called too late.

3. This patch might be reversed:

http://gcc.gnu.org/ml/gcc-patches/2005-03/msg01869.html

If the regression returns, I will try to find --param options that cause 
the ICE on a clean tree.



-- 


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


  parent reply	other threads:[~2005-03-20 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 20:26 [Bug middle-end/20521] New: " bredelin at ucla dot edu
2005-03-17 20:28 ` [Bug middle-end/20521] " bredelin at ucla dot edu
2005-03-20 11:25 ` belyshev at depni dot sinp dot msu dot ru
2005-03-20 15:57 ` bredelin at ucla dot edu [this message]
2005-06-14 19:22 ` pinskia at gcc dot gnu dot 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=20050320155725.28185.qmail@sourceware.org \
    --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).