public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/4895: Athlon not supported by configure. Athlon options undocumented
Date: Wed, 02 Oct 2002 20:06:00 -0000 [thread overview]
Message-ID: <20021003030600.14712.qmail@sources.redhat.com> (raw)
The following reply was made to PR other/4895; it has been noted by GNATS.
From: Phil Edwards <phil@jaj.com>
To: gerald@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nzook@bga.com,
gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: other/4895: Athlon not supported by configure. Athlon options undocumented
Date: Wed, 2 Oct 2002 23:00:02 -0400
On Mon, Sep 09, 2002 at 08:21:47PM -0000, gerald@gcc.gnu.org wrote:
> Synopsis: Athlon not supported by configure. Athlon options undocumented
>
> State-Changed-From-To: open->feedback
> State-Changed-By: gerald
> State-Changed-When: Mon Sep 9 13:21:46 2002
> State-Changed-Why:
> As I have been told by one of our developers, these issues
> should have been adressed by now (GCC 3.2). Can you confirm
> this?
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4895
On the trunk, athlon and athlon_* are recognized as valid --target=foo
machines. Documentation has been updated too.
Phil
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002
next reply other threads:[~2002-10-03 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 20:06 Phil Edwards [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-10 8:01 hubicka
2002-09-09 13:21 gerald
2001-11-12 20:16 nzook
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=20021003030600.14712.qmail@sources.redhat.com \
--to=phil@jaj.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).