From: Andrew Cagney <ac131313@cygnus.com>
To: law@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Disable gdb.threads-hp
Date: Fri, 11 Jan 2002 10:19:00 -0000 [thread overview]
Message-ID: <3C3F2CA8.70009@cygnus.com> (raw)
In-Reply-To: <19349.1009490458@porcupine.cygnus.com>
> > A GDB convention is to add an ``OBSOLETE'' prefix to code like this -
> > that way people using search scripts can ignore those lines. In
> > addition, GDB takes a pretty ruthless aproach to such code and deletes
> > it after the next release.
> > > Since this is tcl, I suspect the prefix should be:
> > > # OBSOLETE
> > > can I suggest also adding that.
> FWIW, GDB has a much saner method for dealing with obsolete stuff than GCC;
> hopefully GCC can learn something from how y'all are handling these kinds of
> issues.
Are you sure about this now that we've started looking at obsoleting
half the targets? :-)
> Presumably you just want an OBSOLETE marker at the top of those test files?
It is more like this:
# OBSOLETE # usrthbasic.exp -- Expect script to test gdb with user threads
# OBSOLETE # Copyright (C) 1992 Free Software Foundation, Inc.
# OBSOLETE
I'll post a patch.
Andrew
prev parent reply other threads:[~2002-01-11 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 15:48 law
2001-12-23 1:44 ` Andrew Cagney
2001-12-27 14:02 ` law
2002-01-11 10:19 ` Andrew Cagney [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=3C3F2CA8.70009@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=law@redhat.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