From: Joseph Myers <joseph@codesourcery.com>
To: Michael Matz <matz@suse.de>
Cc: Richard Sandiford <richard.sandiford@arm.com>,
Richard Biener <richard.guenther@gmail.com>,
<gcc-patches@gcc.gnu.org>, <polacek@redhat.com>,
<jason@redhat.com>, <nathan@acm.org>
Subject: Re: [WIP RFC] Add support for keyword-based attributes
Date: Fri, 21 Jul 2023 23:25:40 +0000 [thread overview]
Message-ID: <4ea49f3-954f-e4aa-1721-8258f1bb5f75@codesourcery.com> (raw)
In-Reply-To: <alpine.LSU.2.20.2307171347170.13548@wotan.suse.de>
On Mon, 17 Jul 2023, Michael Matz via Gcc-patches wrote:
> So, essentially you want unignorable attributes, right? Then implement
> exactly that: add one new keyword "__known_attribute__" (invent a better
> name, maybe :) ), semantics exactly as with __attribute__ (including using
> the same underlying lists in our data structures), with only one single
> deviation: instead of the warning you give an error for unhandled
> attributes. Done.
Assuming you also want the better-defined standard rules about how [[]]
attributes appertain to particular entities, rather than the different
__attribute__ rules, that would suggest something like [[!some::attr]] for
the case of attributes that can't be ignored but otherwise are handled
like standard [[]] attributes.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-07-21 23:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 15:56 Richard Sandiford
2023-07-14 17:17 ` Jakub Jelinek
2023-07-16 10:50 ` Richard Sandiford
2023-07-17 13:39 ` Jason Merrill
2023-07-17 14:06 ` Richard Sandiford
2023-07-14 21:14 ` Nathan Sidwell
2023-07-16 10:18 ` Richard Sandiford
2023-07-17 6:38 ` Richard Biener
2023-07-17 8:21 ` Richard Sandiford
2023-07-17 9:05 ` Richard Biener
2023-07-17 13:53 ` Michael Matz
2023-07-21 23:25 ` Joseph Myers [this message]
2023-08-16 10:36 ` Richard Sandiford
2023-08-16 13:22 ` Joseph Myers
2023-08-17 11:24 ` [PATCH] c: Add support for [[__extension__ ...]] Richard Sandiford
2023-08-17 17:07 ` Richard Biener
2023-08-17 18:36 ` Richard Sandiford
2023-08-18 9:51 ` Richard Sandiford
2023-08-18 19:51 ` Joseph Myers
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=4ea49f3-954f-e4aa-1721-8258f1bb5f75@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=matz@suse.de \
--cc=nathan@acm.org \
--cc=polacek@redhat.com \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.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).