public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, marduk@mandatory.net,
	nobody@gcc.gnu.org
Subject: Re: preprocessor/6844: Seg fault when trying to preprocess a file with lots of #define's
Date: Tue, 28 May 2002 07:18:00 -0000	[thread overview]
Message-ID: <20020528141144.19793.qmail@sources.redhat.com> (raw)

Synopsis: Seg fault when trying to preprocess a file with lots of #define's

State-Changed-From-To: open->feedback
State-Changed-By: neil
State-Changed-When: Tue May 28 07:11:43 2002
State-Changed-Why:
    You state that this happened with RH 7.2 GCC, but you
    also claim that you were using GCC 3.1.  AFAIK RH 7.2
    uses their GCC 2.96.  If that is so, you should report
    it to Red Hat and I wilk close this PR.
    
    If it is a 3.1 bug, I can do nothing to fix it unless you
    give me a testcase in the form of a minimum number of files
    to reproduce.  Asking me to try some random kernel is a non-starter.
    
    Please let me know.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6844


             reply	other threads:[~2002-05-28 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28  7:18 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-29 23:22 neil
2002-05-28  5:36 marduk

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=20020528141144.19793.qmail@sources.redhat.com \
    --to=neil@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=marduk@mandatory.net \
    --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).