This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: PING: [RFA] Fix New ARI warning Tue Nov 6 01:58:48 UTC 2012
- From: "Pierre Muller" <pierre dot muller at ics-cnrs dot unistra dot fr>
- To: "'Joel Brobecker'" <brobecker at adacore dot com>
- Cc: "'Pedro Alves'" <palves at redhat dot com>, <devans at sourceware dot org>, <gdb-patches at sourceware dot org>
- Date: Mon, 12 Nov 2012 17:01:06 +0100
- Subject: RE: PING: [RFA] Fix New ARI warning Tue Nov 6 01:58:48 UTC 2012
- References: <20121106015848.GA5296@sourceware.org> <5098efb2.05fd440a.7696.ffffd821SMTPIN_ADDED@mx.google.com> <50995EBB.6070503@redhat.com> <001b01cdc0b6$7e7b67d0$7b723770$@muller@ics-cnrs.unistra.fr> <20121112155053.GS5103@adacore.com>
> -----Message d'origine-----
> De?: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé?: lundi 12 novembre 2012 16:51
> À?: Pierre Muller
> Cc?: 'Pedro Alves'; devans@sourceware.org; gdb-patches@sourceware.org
> Objet?: Re: PING: [RFA] Fix New ARI warning Tue Nov 6 01:58:48 UTC 2012
>
> > There is probably a list of other similar functions that we should
> > obsolete.
>
> Can you tell us which functions you have in mind?
It depends if we only consider GDB specific functions
or also functions which are part of some system headers.
For the second category, a possible solution would be to
add or override the function as a macro that would generate an error
at compilation time,
but I am not sure this is easy to do in a way that would
work for all systems...
We could forbid by this scheme
function like bcmp/bcopy, abort,
even forbidden constants as true or false
See the list of 'Fixed' items at the bottom of the ARI web page.
> > 1-- Brutal method:
> > Remove function from both header and C sources
> > as well as from ARI script.
>
> I'd go with this approach.
As long as we reach an agreement on the method...
Pierre