From: Bernardo Innocenti <bernie@develer.com>
To: DJ Delorie <dj@redhat.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com, ian@wasabisystems.com
Subject: Re: [libiberty] Add ARG_UNUSED as a C++-friendly replacement for ATTRIBUTE_UNUSED
Date: Tue, 13 Jul 2004 08:05:00 -0000 [thread overview]
Message-ID: <40F397B8.6070308@develer.com> (raw)
In-Reply-To: <200407121909.i6CJ9Hxj021491@greed.delorie.com>
DJ Delorie wrote:
> This implementation doesn't address K&R style argument lists, although
> that's soon to be a moot point ;-)
Anyway, I think there's no way to get something like this to work:
foo (a, b, dummy)
char *a;
int b;
ARG_UNUSED (int, dummy);
{
}
> I'd also prefer this definition to be right after the ATTRIBUTE_UNUSED
> definition, rather than randomly added to the end of the file.
OK.
> However, I'm not convinced we need this yet. By the time we require a
> C++ compiler, 3.4.0 will be old enough to require that version.
So we won't be able to bootstrap from third-party C++ compilers?
The ATTRIBUTE_UNUSED macro cannot be made to work with MSVC, CW
or other popular compilers.
Not that I care that much: on any supported host you can always
install an older version of GCC or cross-compile from another host.
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
prev parent reply other threads:[~2004-07-13 8:05 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
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 [this message]
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=40F397B8.6070308@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 \
/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