public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at techfak dot uni-bielefeld dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/15824] [4.0 Regression] uchar redefinition warnings in libcpp
Date: Fri, 08 Oct 2004 15:10:00 -0000 [thread overview]
Message-ID: <20041008151010.20508.qmail@sourceware.org> (raw)
In-Reply-To: <20040604172005.15824.ro@techfak.uni-bielefeld.de>
------- Additional Comments From ro at techfak dot uni-bielefeld dot de 2004-10-08 15:10 -------
Subject: Re: [4.0 Regression] uchar redefinition warnings in libcpp
pinskia at gcc dot gnu dot org writes:
> Does this still happen?
It did when I last bootstrapped mainline on alpha-dec-osf5.1b as of
20040910.
Rainer
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15824
next prev parent reply other threads:[~2004-10-08 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 17:20 [Bug preprocessor/15824] New: " gcc-bugzilla at gcc dot gnu dot org
2004-06-04 17:24 ` [Bug preprocessor/15824] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-10-08 14:50 ` [Bug preprocessor/15824] [4.0 " pinskia at gcc dot gnu dot org
2004-10-08 15:10 ` ro at techfak dot uni-bielefeld dot de [this message]
2004-11-24 14:02 ` cvs-commit at gcc dot gnu dot org
2004-11-24 14:08 ` pinskia 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=20041008151010.20508.qmail@sourceware.org \
--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).