From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Cc: "'Joel Brobecker'" <brobecker@adacore.com>,
"'Pedro Alves'" <palves@redhat.com>,
<devans@sourceware.org>, <gdb-patches@sourceware.org>
Subject: Re: PING: [RFA] Fix New ARI warning Tue Nov 6 01:58:48 UTC 2012
Date: Mon, 12 Nov 2012 16:29:00 -0000 [thread overview]
Message-ID: <87ip9abx9k.fsf@fleche.redhat.com> (raw)
In-Reply-To: <22453.3111825169$1352736109@news.gmane.org> (Pierre Muller's message of "Mon, 12 Nov 2012 17:01:06 +0100")
>>>>> "Pierre" == Pierre Muller <pierre.muller@ics-cnrs.unistra.fr> writes:
Pierre> For the second category, a possible solution would be to
Pierre> add or override the function as a macro that would generate an error
Pierre> at compilation time,
Pierre> but I am not sure this is easy to do in a way that would
Pierre> work for all systems...
IMO it is ok if it doesn't work universally as long as it works for a
large enough subset of gdb developers. This will ensure that most
breakages are caught early.
GCC uses the poison pragma for this. It seems to work well enough.
Tom
next prev parent reply other threads:[~2012-11-12 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 1:59 GDB Administrator
2012-11-06 11:08 ` [RFA] Fix " Pierre Muller
[not found] ` <5098efb2.05fd440a.7696.ffffd821SMTPIN_ADDED@mx.google.com>
2012-11-06 19:02 ` Pedro Alves
2012-11-12 9:17 ` PING: " Pierre Muller
2012-11-12 15:51 ` Joel Brobecker
2012-11-12 16:01 ` Pierre Muller
2012-11-12 16:28 ` Tom Tromey
[not found] ` <22453.3111825169$1352736109@news.gmane.org>
2012-11-12 16:29 ` Tom Tromey [this message]
2012-11-12 17:06 ` Joel Brobecker
[not found] ` <40242.9794231013$1352711862@news.gmane.org>
2012-11-14 16:45 ` Tom Tromey
2012-11-15 8:14 ` Pierre Muller
2012-11-15 8:32 ` Pierre Muller
[not found] ` <50a4a88c.47f0440a.4029.ffff805aSMTPIN_ADDED@mx.google.com>
2012-11-15 11:36 ` Pedro Alves
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=87ip9abx9k.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=devans@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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