From: Ian Lance Taylor <iant@google.com>
To: lexa@dm.botik.ru (Alexey I. Adamovich)
Cc: gcc@gcc.gnu.org
Subject: Re: Help ! Frozen by a comment in gcc/c-common.h!
Date: Mon, 31 Aug 2009 18:23:00 -0000 [thread overview]
Message-ID: <m3eiqst2cn.fsf@google.com> (raw)
In-Reply-To: <20090829194244.GA20643@dm.botik.ru> (Alexey I. Adamovich's message of "Sat\, 29 Aug 2009 23\:42\:44 +0400")
lexa@dm.botik.ru (Alexey I. Adamovich) writes:
> Forgot RID_LAST_MODIFIER
>
> On Sat, Aug 29, 2009 at 08:29:21PM +0400, Alexei I. Adamovich wrote:
>> So for the sake of those who will develop C-derived front ends, should
>> we change the comment like below:
>> > /* Reserved identifiers. This is the union of all the keywords for C,
>> > C++, and Objective-C. In the past, in earlier GCC versions all the
>> > type modifiers had to be in one block at the beginning, because
>> > they were used as mask bits. There were 27 type modifiers; so if
>> > anybody added many more the mask mechanism would have to be
>> > redesigned. Now it doesn't matter, since corresponding mask
>> > machinery gone */
>
> Should the last lines be re-written as follows:
>> redesigned. Now it doesn't matter, since corresponding mask
>> machinery gone. But anyway when adding any type modifier it's
>> better to follow the old rule and to get sure that
>> RID_LAST_MODIFIER is defined and handled correctly also */
> [?]
I think we should drop the reference to previous gcc versions and the
old scheme. I don't think it helps in understanding the code.
It's still necessary to set RID_LAST_MODIFIER correctly as
declspecs_add_type uses it.
Ian
next prev parent reply other threads:[~2009-08-31 15:44 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
2009-08-30 3:04 ` Alexei I. Adamovich
2009-08-30 6:58 ` Alexey I. Adamovich
2009-08-31 18:23 ` Ian Lance Taylor [this message]
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=m3eiqst2cn.fsf@google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=lexa@dm.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).