public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/6994: ICE in find_function_data
Date: Wed, 09 Oct 2002 16:06:00 -0000	[thread overview]
Message-ID: <20021009230601.9200.qmail@sources.redhat.com> (raw)

The following reply was made to PR middle-end/6994; it has been noted by GNATS.

From: Janis Johnson <janis187@us.ibm.com>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, adrian@suse.de,
   schwab@suse.de
Cc:  
Subject: Re: middle-end/6994: ICE in find_function_data
Date: Wed, 9 Oct 2002 16:00:59 -0700

 This problem still exists in 3.3 20021008 and 3.2.1 20021009 on
 i686-pc-linux-gnu.  As mentioned earlier, it's a regression from
 GCC 2.95.3.
 
 The PR name ought to be "c++" rather than "middle-end".
 
 At the time of the ICE in find_function_data, 'exp' in expand_expr is
 a SAVE_EXPR whose function context, 'context', is cloned from
 'current_function_decl'.  The code in expand_expr falsely assumes that
 since 'context' is different from 'current_function_decl', 'context' is
 a containing function.  It calls find_function_data just to make sure
 that 'context' is for a containing function, but it's not so that
 function aborts.
 
 I don't where to go from here, but hope that this information will be
 of use to someone familiar with the C++ front end.
 
 Janis


             reply	other threads:[~2002-10-09 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 16:06 Janis Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-13 22:49 Reichelt
2002-06-12  6:46 Reichelt
2002-06-11  8:26 schwab

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=20021009230601.9200.qmail@sources.redhat.com \
    --to=janis187@us.ibm.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).