public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8338: Infinite loop on illegal code
Date: Thu, 31 Oct 2002 14:06:00 -0000	[thread overview]
Message-ID: <20021031220601.12105.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/8338; it has been noted by GNATS.

From: Joe Buck <jbuck@synopsys.com>
To: gcc-gnats@gcc.gnu.org, dv@vollmann.ch, gcc-bugs@gcc.gnu.org
Cc:  
Subject: Re: c++/8338: Infinite loop on illegal code
Date: Thu, 31 Oct 2002 13:58:33 -0800

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8338
 
 With 20021031 from the 3.2 branch, I am not seeing an infinite loop; I 
 get an ICE.
 The ICE is a segmentation fault in cc1plus, in walk_tree in 
 tree-inline.c.  The
 ICE happens quickly, there is no excessive memory consumption.
 
 


             reply	other threads:[~2002-10-31 22:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 14:06 Joe Buck [this message]
2002-11-06 18:05 mmitchel
2002-11-07 17:45 mmitchel

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=20021031220601.12105.qmail@sources.redhat.com \
    --to=jbuck@synopsys.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).