This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Joy with new GCC 3.3 warnings -- HTF to shut them up?

From: prj at po dot cwru dot edu (Paul Jarc)
To: Gabriel Dos Reis <gdr at integrable-solutions dot net>
Cc: Joe Buck <jbuck at synopsys dot com>, "Cook, Kelley \(R.K.\)" <kcook34 at ford dot com>, "'David O'Brien'" <obrien at freebsd dot org>, "'GCC'" <gcc at gcc dot gnu dot org>
Date: Fri, 02 May 2003 10:52:33 -0400
Subject: Re: Joy with new GCC 3.3 warnings -- HTF to shut them up?
Organization: What did you have in mind? A short, blunt, human pyramid?
References: <E70D26A9CDD5C04D806EB8CA831D07210FC506@na1ecm61.dearborn.ford.com><20030501091710.A21602@synopsys.com><m33cjxpks9.fsf@uniton.integrable-solutions.net>

Gabriel Dos Reis <gdr@integrable-solutions.net> wrote:
> The syntax of __attribute__ is advantageously crafted so that it can
> be #define __attribute__(a)  /* nothing */

It's possible, though, that other compilers may have their own,
unrelated meaning for __attribute__ which is incompatible with such a
definition.  void violating the standard, you have to use something
like:
#ifdef __GNUC__
#define myattr(a) __attribute__(a)
#else
#define myattr(a)
#endif
But this is still not much work.

paul

Follow-Ups:
- Re: Joy with new GCC 3.3 warnings -- HTF to shut them up?
  - From: Paul Jarc

References:
- Re: Joy with new GCC 3.3 warnings -- HTF to shut them up?
  - From: Cook, Kelley (R.K.)
- Re: Joy with new GCC 3.3 warnings -- HTF to shut them up?
  - From: Joe Buck
- Re: Joy with new GCC 3.3 warnings -- HTF to shut them up?
  - From: Gabriel Dos Reis

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]