From: Tom Tromey <tromey@redhat.com>
To: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: [incremental] Patch: FYI: fix hole in c_token
Date: Tue, 13 Nov 2007 00:39:00 -0000 [thread overview]
Message-ID: <m3k5onf6e4.fsf@fleche.redhat.com> (raw)
I'm checking this in on the incremental-compiler branch.
When I added the user_owned field to c_token, I increased its size by
a whole word. This patch fixes the problem by reducing the width of
the pragma_kind field.
Tom
ChangeLog:
2007-11-12 Tom Tromey <tromey@redhat.com>
* c-pragma.c (c_register_pragma_1): Update.
* c-parser.c (c_token) <pragma_kind>: Use 6 bits, not 7.
Index: c-pragma.c
===================================================================
--- c-pragma.c (revision 130053)
+++ c-pragma.c (working copy)
@@ -885,7 +885,7 @@
id += PRAGMA_FIRST_EXTERNAL - 1;
/* The C++ front end allocates 6 bits in cp_token; the C front end
- allocates 7 bits in c_token. At present this is sufficient. */
+ allocates 6 bits in c_token. At present this is sufficient. */
gcc_assert (id < 64);
cpp_register_deferred_pragma (parse_in, space, name, id,
Index: c-parser.c
===================================================================
--- c-parser.c (revision 130057)
+++ c-parser.c (working copy)
@@ -257,7 +257,7 @@
ENUM_BITFIELD (rid) keyword : 8;
/* If this token is a CPP_PRAGMA, this indicates the pragma that
was seen. Otherwise it is PRAGMA_NONE. */
- ENUM_BITFIELD (pragma_kind) pragma_kind : 7;
+ ENUM_BITFIELD (pragma_kind) pragma_kind : 6;
/* True if this token is from a system header. */
BOOL_BITFIELD in_system_header : 1;
/* True if this token comes from a header owned by the user. */
reply other threads:[~2007-11-12 22:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3k5onf6e4.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gcc-patches@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).