Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: muller@ics.u-strasbg.fr (Pierre Muller)
Cc: brobecker@adacore.com ('Joel Brobecker'), gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbadmin/ss/gdb_ari.sh obsolete->regression
Date: Wed, 15 Apr 2009 13:52:00 -0000	[thread overview]
Message-ID: <200904151352.n3FDqCcQ021342@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <000401c9bd99$89bb01b0$9d310510$@u-strasbg.fr> from "Pierre Muller" at Apr 15, 2009 09:12:29 AM

Pierre Muller wrote:

>   I would tend to agree with you,
> but it's just more work...
>   So if anyone is volunteering, fine with me,
> I doubt that I will have time to eradicate all
> those unused macros from sources.
> 
> Pierre
> 
> PS: I also think that it would probably be good to
> leave the unused functions/macros in at least one
> GDB release, as people using GDB source code
> might still be using such obsolete code,
> especially if it was not deprecate'd.

It seems me the point of the ARI "regression" category
is to help catch adding back code patterns that we've
already managed to get rid of.  This makes perfect sense
for code patterns that *can* get added back accidentally
(e.g. coding style violations etc.).

However, some code patterns that are currently listed
as ARI regressions *cannot* be added back accidentally
anyway; for example, there is an ARI regression check
for use of the read_register function -- this function
is not even defined anywhere in the GDB source tree
today, so any attempt to call it would already cause
compile/link time failures.

I'd argue that ARI tests like those ought to be simply
deleted; they serve no further purpose.


B.t.w. as you're clearing up ARI results anyway (b.t.w.
thank you for your efforts in this area!), there's a
number of ARI tests where all remaining hits are in
fact false positives:

In the Obsolete category:

supply_register  (this function no longer exists; ARI
finds local struct members with the same name as false
positive results)

inside_entry_func  (this is now a static routine; the
original reason for this ARI entry no longer applies)

In the Deprecate category:

SP_REGNUM, PC_REGNUM, FP0_REGNUM   (these are not defined
anywhere any more; ARI finds local definitions with 
extended names like E_SP_REGNUM etc.)

In the Legacy category:

legacy_name  (this doesn't exist any more; ARI finds a
local variable with the same name)

I think these should also be simply deleted ...


Bye,
Ulrich


-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2009-04-15 13:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 21:21 Pierre Muller
2009-04-15  6:38 ` Joel Brobecker
2009-04-15  7:12   ` Pierre Muller
2009-04-15 13:52     ` Ulrich Weigand [this message]
2009-04-16  9:35       ` Joel Brobecker
2009-04-17 11:23         ` Pierre Muller
2009-04-17 11:53           ` Ulrich Weigand
2009-04-16  7:16     ` Joel Brobecker

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=200904151352.n3FDqCcQ021342@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.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