This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Dealing with warnings on __attribute__((user)) when dehydra is not loaded
- From: Tom Tromey <tromey at redhat dot com>
- To: Benjamin Smedberg <benjamin at smedbergs dot us>
- Cc: Diego Novillo <dnovillo at google dot com>, gcc at gcc dot gnu dot org
- Date: Fri, 16 Oct 2009 10:59:36 -0600
- Subject: Re: Dealing with warnings on __attribute__((user)) when dehydra is not loaded
- References: <b798aad50910160517j1dc6be5bkccb9bc97901f4d4c@mail.gmail.com> <mailman.5536.1255709509.4294.dev-static-analysis@lists.mozilla.org> <4AD8A084.2010206@smedbergs.us>
- Reply-to: Tom Tromey <tromey at redhat dot com>
>>>>> "Benjamin" == Benjamin Smedberg <benjamin@smedbergs.us> writes:
Benjamin> Dehydra is going to switch from the generic user attribute to
Benjamin> specific GCC-registered attributes __attribute__((NS_final))
Benjamin> at some point when one of us can code it up.
Benjamin> I don't particularly like __attribute__((plugin (pluginname,
Benjamin> arg))). You're forced to code plugin names into your source,
Benjamin> when you may not actually know the name of the plugin that's
Benjamin> going to process your annotations.
Yeah, that makes sense.
It seems to me that there are two problems here. One is the namespace
problem, and the other is avoiding warnings for certain attributes.
Registering attributes by name solves the first one but not the second.
Tom