public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "levon at movementarian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/12480] PCH prevents "compilation of header file requested" warning
Date: Wed, 01 Oct 2003 18:02:00 -0000 [thread overview]
Message-ID: <20031001180213.14097.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031001174525.12480.levon@movementarian.org>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12480
levon at movementarian dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |minor
------- Additional Comments From levon at movementarian dot org 2003-10-01 18:02 -------
How is it not a bug ?
A QoS issue, perhaps, but nonetheless. Suddenly a standard build
of GCC means you can never get the helpful error any more, and you
get some meaningless crap (meaningless to someone who does not know
what .gch is used for).
next prev parent reply other threads:[~2003-10-01 18:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 17:45 [Bug pch/12480] New: " levon at movementarian dot org
2003-10-01 17:47 ` [Bug pch/12480] " pinskia at gcc dot gnu dot org
2003-10-01 18:02 ` levon at movementarian dot org [this message]
2003-10-01 18:08 ` pinskia at gcc dot gnu dot org
2003-10-01 18:29 ` zack at gcc dot gnu dot org
2003-10-01 18:40 ` levon at movementarian dot org
2003-10-01 18:57 ` levon at movementarian dot org
2003-10-02 18:15 ` [Bug pch/12480] pch error messages do say they for PCH pinskia at gcc dot gnu dot org
2003-12-16 18:40 ` [Bug pch/12480] pch error messages do not " geoffk at gcc dot gnu dot org
2003-12-17 23:06 ` cvs-commit at gcc dot gnu dot org
2003-12-18 0:04 ` geoffk at gcc dot gnu dot org
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=20031001180213.14097.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).