public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7585: Attributes for nested typedef-name ignored Date: Thu, 31 Oct 2002 07:26:00 -0000 [thread overview] Message-ID: <20021031152602.5532.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7585; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Gabriel Dos Reis <gdr@integrable-solutions.net> Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org> Subject: Re: c++/7585: Attributes for nested typedef-name ignored Date: Thu, 31 Oct 2002 09:21:27 -0600 (CST) > | I can see this as well, but I imagine the syntax is wrong: > | shouldn't it be > | typedef struct { } __attribute__((__aligned__(__alignof__(int)))) Y; > | > | instead of > | > | typedef struct { } Y __attribute__((__aligned__(__alignof__(int)))); > | > | ?? > > Maybe. But then, I think __alignof__(Y) should return > __alignof__(int) if the attribute is being applied to Y. > > Said differently, what do you envision for the "right" syntax for > > typedef unsigned char type[sizeof(int)] > __attribute__((__aligned__(__alignof__(int)))); I have no clue. I think that the weird C declaration syntax is probably just not suited for the application of attributes. And maybe it's simpler to understand if you make up the typedef in steps, say typedef unsigned char array[...] typedef aligne_array __attribute__(...) aligned_array; (or the attributes somewhere else). I think it would help to have a formal specification of attribute placement somewhere. Although it would probably be so complicated that nobody would want to read it... Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-10-31 15:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-31 7:26 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-31 11:26 Joseph S. Myers 2002-10-31 9:16 Gabriel Dos Reis 2002-10-30 20:16 Gabriel Dos Reis 2002-10-30 16:32 bangerth 2002-08-13 9:36 gdr
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=20021031152602.5532.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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: linkBe 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).