From: Ian Lance Taylor <iant@google.com>
To: "Alexei I. Adamovich" <lexa@adam.botik.ru>
Cc: gcc@gcc.gnu.org
Subject: Re: Help ! Frozen by a comment in gcc/c-common.h!
Date: Fri, 28 Aug 2009 04:53:00 -0000 [thread overview]
Message-ID: <m3hbvtyzcd.fsf@google.com> (raw)
In-Reply-To: <20090827115025.GA7870@adam.botik.ru> (Alexei I. Adamovich's message of "Thu\, 27 Aug 2009 15\:50\:25 +0400")
"Alexei I. Adamovich" <lexa@adam.botik.ru> writes:
> While modifying the C lexer to accommodate it for experimental
> C-derived language front-end, I've stumbled across the following
> comment in gcc/c-common.h before the "enum rid" definition (still
> there in gcc-4.5-20090820 snapshot):
>
> 42 /* Reserved identifiers. This is the union of all the keywords for C,
> 43 C++, and Objective-C. All the type modifiers have to be in one
> 44 block at the beginning, because they are used as mask bits. There
> 45 are 27 type modifiers; if we add many more we will have to redesign
> 46 the mask mechanism. */
> 47
> 48 enum rid
> 49 {
> 50 /* Modifiers: */
> 51 /* C, in empirical order of frequency. */
> 52 RID_STATIC = 0,
> 53 RID_UNSIGNED, RID_LONG, RID_CONST, RID_EXTERN
> ...
>
> Could you please enlighten me -- is the comment still relevant? If so,
> where the usage of type modifiers entries in enum rid as mask bits can
> be seen in gcc code (or documentation, if applicable)?
I suspect that that comment is no longer relevant. At least, I can't
seem to find the mask. Perhaps somebody else knows.
Ian
next prev parent reply other threads:[~2009-08-27 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 13:29 Alexei I. Adamovich
2009-08-28 4:53 ` Ian Lance Taylor [this message]
2009-08-30 3:04 ` Alexei I. Adamovich
2009-08-30 6:58 ` Alexey I. Adamovich
2009-08-31 18:23 ` Ian Lance Taylor
2009-08-31 19:27 ` Alexey I. Adamovich
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=m3hbvtyzcd.fsf@google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=lexa@adam.botik.ru \
/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).