This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Cleaning and extening the diagnostics machinery
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Subject: Re: [RFC] Cleaning and extening the diagnostics machinery
- From: Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>
- Date: 31 May 2001 21:40:31 +0200
- Cc: Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>, <gcc at gcc dot gnu dot org>, Zack Weinberg <zackw at Stanford dot EDU>
- Organization: CMLA, ENS Cachan -- CNRS UMR 8536 (France)
- References: <Pine.LNX.4.33.0105311902530.20744-100000@kern.srcf.societies.cam.ac.uk>
"Joseph S. Myers" <jsm28@cam.ac.uk> writes:
| On 31 May 2001, Gabriel Dos Reis wrote:
|
| > A warning for an unimplemented fonctionality? What usage do you see
| > for it?
|
| There are at least a couple of uses of this in the C front end:
|
| c-parse.in (typename):
|
| /* We don't yet support attributes here. */
| if (attrs != NULL_TREE)
| warning ("attributes on type name ignored");
|
| (There are many places where attributes ought to work, but don't and have
| funny effects. The normal practice of GCC on attributes it doesn't
| understand or handle is to ignore them with a warning - in this case, the
| attributes may be valid, but this place for them isn't implemented.)
Thanks a lot for these detailed helpful explanations.
-- Gaby