From: Nathanael Nerode <neroden@doctormoo.dyndns.org>
To: gcc@gcc.gnu.org
Cc: binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: obselete configurations & the top level
Date: Sun, 26 May 2002 22:23:00 -0000 [thread overview]
Message-ID: <20020527052330.GA25946@doctormoo.dyndns.org> (raw)
This is a query. A bunch of configurations have been obseleted and
removed from GCC recently. These have all, I believe, been obseleted
and removed from GDB already.
There is special-case code for many of these configurations in
configure.in. I would like to get rid of it.
What else do I need to check before I get rid of these cases? Are any
of them possibly still supported by binutils?
Please see http://gcc.gnu.org/ml/gcc-patches/2002-05/msg01994.html for
the list of configurations which are going away, where I'd like to see
if I can strip stuff out of the top level too.
I intend to submit a cleanup patch for this once I'm sure I'm not
deleting anything which is still supported somewhere.
Thanks in advance.
--Nathanael Nerode
neroden@twcny.rr.com
next reply other threads:[~2002-05-27 5:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-26 22:23 Nathanael Nerode [this message]
2002-05-26 22:43 ` Stan Shebs
2002-05-27 2:38 Christian Groessler
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=20020527052330.GA25946@doctormoo.dyndns.org \
--to=neroden@doctormoo.dyndns.org \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.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