From: Joseph Myers <joseph@codesourcery.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: "Martin Liška" <mliska@suse.cz>,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
"Jason Merrill" <jason@redhat.com>,
"Marek Polacek" <polacek@redhat.com>,
iant@golang.org
Subject: Re: [PATCH][RFC] Canonize names of attributes.
Date: Wed, 14 Jun 2017 16:40:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1706141630080.14610@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAFiYyc0Zyg9KK8Zf_XAxKiuvjUHSDkMoSBwOD7e13xdi-pOeVw@mail.gmail.com>
On Wed, 14 Jun 2017, Richard Biener wrote:
> >> are you sure this is needed? This seems to be solely arguments to
> >> attributes.
> >
> > It's need for cases like:
> > __intN_t (8, __QI__);
>
> But __QI__ is not processed in lookup_attribute, is it? So canonizing that
> looks unrelated? I didn't see similar handling in the C FE btw (but
> maybe I missed it).
It's not clear to me that there is automatically a rule that where
identifiers are arguments to attributes, they must follow this rule about
foo and __foo__ being equivalent.
Specifically: c-attribs.c:attribute_takes_identifier_p says that the
cleanup attribute takes an identifier (a function name). But it's
certainly the case that the exact function named there must be used; foo
and __foo__ as cleanup attribute arguments are not equivalent. (You could
argue cleanup should take an expression, with an error then being given if
that doesn't evaluate to a function designator.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-06-14 16:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 12:32 Martin Liška
2017-06-13 13:20 ` Richard Biener
2017-06-14 7:48 ` Martin Liška
2017-06-14 9:07 ` Richard Biener
2017-06-14 11:03 ` Martin Liška
2017-06-14 11:19 ` Richard Biener
2017-06-14 16:40 ` Joseph Myers [this message]
2017-06-28 14:45 ` Martin Liška
2017-06-14 17:24 ` Jason Merrill
2017-06-16 0:07 ` Martin Sebor
2017-06-28 14:46 ` Martin Liška
2017-06-28 16:06 ` Joseph Myers
2017-06-28 19:01 ` Jason Merrill
2017-06-30 9:23 ` [PATCH v2][RFC] " Martin Liška
2017-06-30 19:35 ` Jason Merrill
2017-07-03 9:52 ` Martin Liška
2017-07-03 21:00 ` Jason Merrill
2017-07-11 13:38 ` Martin Liška
2017-07-11 15:52 ` Jason Merrill
2017-07-13 13:48 ` Martin Liška
2017-07-13 13:51 ` [RFC][PATCH] Do refactoring of attribute functions and move them to attribs.[hc] Martin Liška
2017-07-14 7:23 ` Jeff Law
2017-07-14 7:40 ` Martin Liška
2017-08-04 13:53 ` Martin Liška
2017-08-08 4:37 ` Martin Liška
2017-08-08 9:14 ` Tom de Vries
2017-09-12 7:55 ` Jakub Jelinek
2017-09-12 11:31 ` Martin Liška
2017-09-12 11:40 ` Jakub Jelinek
2017-09-12 14:25 ` Martin Liška
2017-07-27 12:57 ` [PATCH v2][RFC] Canonize names of attributes Martin Liška
2017-08-02 11:25 ` Joseph Myers
2017-08-04 13:43 ` Martin Liška
2017-08-04 16:54 ` Jason Merrill
2017-08-07 16:44 ` [PATCH][OBVIOUS] Fix missing include of header file in mips.c Martin Liška
2017-08-07 17:10 ` [PATCH][OBVIOUS] Add missing header file attribs.h to couple of targets Martin Liška
2017-08-02 19:42 ` [PATCH v2][RFC] Canonize names of attributes 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=alpine.DEB.2.20.1706141630080.14610@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@golang.org \
--cc=jason@redhat.com \
--cc=mliska@suse.cz \
--cc=polacek@redhat.com \
--cc=richard.guenther@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).