From: Geoffrey Keating <geoffk@apple.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: Using __extension__ in a struct with a GTY(()) mark
Date: Thu, 03 Apr 2003 01:23:00 -0000 [thread overview]
Message-ID: <D67E4044-6568-11D7-9604-0030657EA24A@apple.com> (raw)
In-Reply-To: <200304022300.SAA17030@caip.rutgers.edu>
On Wednesday, April 2, 2003, at 03:00 PM, Kaveh R. Ghazi wrote:
> The problem I'm having now is that I need to add the __extension__
> keyword to the struct so that it doesn't get a complaint from GCC.
> Not being very fluent in bison or flex, I can't seem to get gengtype
> to accept it.
You want to simply ignore the __extension__, right?
If so, you can put it after
"const"/[^[:alnum:]_] /* don't care */
like
"__extension__"/[^[:alnum:]_] /* ignore */
in gengtype-lex.l.
> In the end, I'm trying to get this struct parsed by gengtype:
>
> struct lang_type_header GTY(()) __extension__
> {
> CHAR_BITFIELD is_lang_type_class : 1;
>
> CHAR_BITFIELD has_type_conversion : 1;
> CHAR_BITFIELD has_init_ref : 1;
> CHAR_BITFIELD has_default_ctor : 1;
> CHAR_BITFIELD uses_multiple_inheritance : 1;
> CHAR_BITFIELD const_needs_init : 1;
> CHAR_BITFIELD ref_needs_init : 1;
> CHAR_BITFIELD has_const_assign_ref : 1;
> };
>
> Please help?
>
> Thanks,
> --Kaveh
> --
> Kaveh R. Ghazi ghazi@caip.rutgers.edu
>
--
Geoff Keating <geoffk@apple.com>
next prev parent reply other threads:[~2003-04-03 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 0:11 Kaveh R. Ghazi
2003-04-03 1:23 ` Geoffrey Keating [this message]
2003-04-03 6:45 ` Kaveh R. Ghazi
2003-04-03 3:17 ` Jason Merrill
2003-04-03 5:57 ` Kaveh R. Ghazi
2003-04-03 6:15 ` Jason Merrill
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=D67E4044-6568-11D7-9604-0030657EA24A@apple.com \
--to=geoffk@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
/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).