public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <gnats@kayari.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/7741: ICE on conflicting types
Date: Sun, 08 Sep 2002 06:06:00 -0000	[thread overview]
Message-ID: <20020908130600.16236.qmail@sources.redhat.com> (raw)

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

From: Jonathan Wakely <gnats@kayari.org>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
   nobody@gcc.gnu.org
Cc:  
Subject: Re: c/7741: ICE on conflicting types
Date: Sun, 8 Sep 2002 14:03:43 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7741
 
 The preprocessed source removed the comment I'd made about what caused the
 ICE. Removing the #include <unistd.h> prevents the ICE, and a proper
 diagnostic message is issued about the conflicting type declarations.
 Including unistd.h causes the ICE (so it might be something screwy on my
 system - but it doesn't happen with GCC 3.0)
 
 jon
 


             reply	other threads:[~2002-09-08 13:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-08  6:06 Jonathan Wakely [this message]
2002-12-04 12:56 Jonathan Wakely

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=20020908130600.16236.qmail@sources.redhat.com \
    --to=gnats@kayari.org \
    --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).