public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gavin Ray <ray.gavin97@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Using [[may_alias]] in C23/C++23 on a union works in neither post-"union" position, or at the end of the definition
Date: Tue, 6 Dec 2022 15:31:57 -0500	[thread overview]
Message-ID: <CAFtvWZMxmeeZY8QpODgTQmvBRAR62hDaqwN6D2XCvnY8JmFikw@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRmX72shEPmsX2ajB7uU16svwkXUGc-6jiVRZbOwxm85A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 673 bytes --]

Ah got it, didn't know that (handy, will save me duplicating a bunch of
attributes).
Thanks Jonathan!

On Tue, Dec 6, 2022 at 2:23 PM Jonathan Wakely <jwakely.gcc@gmail.com>
wrote:

>
>
> On Tue, 6 Dec 2022, 18:36 Gavin Ray via Gcc, <gcc@gcc.gnu.org> wrote:
>
>> Oh, D'oh! Thanks Joseph, apologies for the needless email on the list
>> then.
>>
>> One final question if I could -- does that mean that in order to support
>> "may-alias" with the bracket syntax on both Clang and GCC, it would
>> require:
>>
>>  union [[gnu::may_alias]] [[clang::may_alias]] foo {};
>>
>
>
>
> Probably not. Clang accepts the gnu:: namespace for attributes that
> originated with GCC.
>
>
>

  reply	other threads:[~2022-12-06 20:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06  3:17 Gavin Ray
2022-12-06 16:54 ` Joseph Myers
2022-12-06 18:35   ` Gavin Ray
2022-12-06 19:23     ` Jonathan Wakely
2022-12-06 20:31       ` Gavin Ray [this message]
2022-12-06 20:36         ` Jonathan Wakely

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=CAFtvWZMxmeeZY8QpODgTQmvBRAR62hDaqwN6D2XCvnY8JmFikw@mail.gmail.com \
    --to=ray.gavin97@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=jwakely.gcc@gmail.com \
    /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).