public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: zack@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: c/6300
Date: Mon, 22 Apr 2002 15:36:00 -0000 [thread overview]
Message-ID: <20020422223601.22947.qmail@sources.redhat.com> (raw)
The following reply was made to PR c/6300; it has been noted by GNATS.
From: zack@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org
Cc:
Subject: c/6300
Date: 22 Apr 2002 22:26:07 -0000
CVSROOT: /cvs/gcc
Module name: gcc
Branch: gcc-3_1-branch
Changes by: zack@gcc.gnu.org 2002-04-22 15:26:07
Modified files:
gcc : ChangeLog c-lex.c config.gcc
gcc/doc : install.texi
Log message:
* c-lex.c (lex_charconst): Call convert to get constant in
proper type; don't just smash the type field.
Fixes PR c/6300.
* config.gcc: Add list of obsolete configurations. Disallow
building these without --enable-obsolete.
* doc/install.texi: Document --enable-obsolete and obsoletion
policy. Mention obsoletion of individual targets in
appropriate places.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.13152.2.431&r2=1.13152.2.432
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/c-lex.c.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.164.2.2&r2=1.164.2.3
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config.gcc.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.167.2.14&r2=1.167.2.15
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/doc/install.texi.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.92.2.13&r2=1.92.2.14
next reply other threads:[~2002-04-22 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 15:36 zack [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-22 15:26 c/6300 zack
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=20020422223601.22947.qmail@sources.redhat.com \
--to=zack@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: 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).