From: Bernardo Innocenti <bernie@develer.com>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
gdb-patches@sources.redhat.com, binutils@sources.redhat.com,
Ian Lance Taylor <ian@wasabisystems.com>,
DJ Delorie <dj@redhat.com>
Subject: Re: [libiberty] Add ARG_UNUSED as a C++-friendly replacement for ATTRIBUTE_UNUSED
Date: Tue, 13 Jul 2004 07:50:00 -0000 [thread overview]
Message-ID: <40F3944C.1000502@develer.com> (raw)
In-Reply-To: <200407120419.i6C4Jq318362@tin.geop.uc.edu>
Andrew Pinski wrote:
>>this patch adds the ARG_UNUSED() macro to be used in place of
>>ATTRIBUTE_UNUSED. The syntax looks like this:
>>
>> void foo (ARG_UNUSED (int, x))
>> {
>> }
>>
>>The C++ frontend can't parse attribute((unused)) when it
>>appears after the variable name. The cleanest work-around
>>is using the standard C++ syntax to specify unused
>>parameters, which can also be used when bootstrapping from
>>other C++ compilers.
>>
>>This patch is a prerequisite for the upcoming C++ bootstrap
>>patches that I've been preparing.
>
>
> Huh? Yes it can from 3.4.0 and above.
Nevertheless, bootstrap from earlier versions of GCC
would fail (I was using Apple's version of GCC 3.3).
ansidecl.h enables ATTRIBUTE_UNUSED for any GCC > 2.7.
We could make the check stricter, like this:
#if !defined(__cplusplus) || GCC_VERSION >= 3004
#define ATTRIBUTE_UNUSED __attribute__ ((__unused__))
#endif
But I'd much prefer the ARG_UNUSED solution, which can
be made to work with and C or C++ compiler, using whatever
funny syntax the compiler requires.
This macro is in libiberty, which is about portability
across different OSes and compilers.
I also like the ARG_UNUSED syntax because it's somewhat
shorter to type. (btw, Doxygen can parse it if you
define ARG_UNUSED(T,N) to "T N").
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
next prev parent reply other threads:[~2004-07-13 7:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-11 23:52 Bernardo Innocenti
2004-07-12 4:20 ` Andrew Pinski
2004-07-13 7:50 ` Bernardo Innocenti [this message]
2004-07-13 8:12 ` Richard Henderson
2004-07-13 8:15 ` Bernardo Innocenti
2004-07-13 8:51 ` Richard Henderson
2004-07-13 17:11 ` Jason Merrill
[not found] ` <Pine.LNX.4.56.0407132255170.4658@hades.cambridge.redhat.com>
2004-07-13 22:45 ` Bernardo Innocenti
2004-07-12 14:01 ` Andrew Cagney
2004-07-12 19:09 ` DJ Delorie
2004-07-13 8:05 ` Bernardo Innocenti
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=40F3944C.1000502@develer.com \
--to=bernie@develer.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ian@wasabisystems.com \
--cc=pinskia@physics.uc.edu \
/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