public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: neil@gcc.gnu.org To: dickey@radix.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: preprocessor/7040: gcc 3.x cannot compile its own preprocessor output Date: Sun, 16 Jun 2002 14:57:00 -0000 [thread overview] Message-ID: <20020616213656.24577.qmail@sources.redhat.com> (raw) Synopsis: gcc 3.x cannot compile its own preprocessor output State-Changed-From-To: feedback->open State-Changed-By: neil State-Changed-When: Sun Jun 16 14:36:54 2002 State-Changed-Why: In fact, I think 3.0.4 is fixed too. Please let me know what you used; 3.x is not helpful. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7040
next reply other threads:[~2002-06-16 21:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-16 14:57 neil [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-24 14:46 neil 2002-06-21 17:53 Thomas Dickey 2002-06-18 4:36 neil 2002-06-16 14:37 neil 2002-06-15 10:46 dickey
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=20020616213656.24577.qmail@sources.redhat.com \ --to=neil@gcc.gnu.org \ --cc=dickey@radix.net \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.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: linkBe 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).