From: "H. J. Lu" <hjl@lucon.org>
To: Andreas Jaeger <aj@suse.de>
Cc: Daniel Berlin <dberlin@dberlin.org>, gcc@gcc.gnu.org
Subject: Re: Bugzilla CPU targets
Date: Thu, 22 May 2003 07:08:00 -0000 [thread overview]
Message-ID: <20030522000216.A6832@lucon.org> (raw)
In-Reply-To: <ho7k8jh3o8.fsf@byrd.suse.de>; from aj@suse.de on Thu, May 22, 2003 at 08:54:31AM +0200
On Thu, May 22, 2003 at 08:54:31AM +0200, Andreas Jaeger wrote:
> "H. J. Lu" <hjl@lucon.org> writes:
>
> > One thing I missed the most is CPU targets. Can we add ia32, ia64,
> > mips, alpha, ppc, .....?
>
> You can search for host/target/build, isn't that enough?
>
You can make your own host/target/build. What I like to see a drop
down menu to select the valid ones. Also in most cases, a backend bug
is indepedent of host/target/build OSes.
H.J.
next prev parent reply other threads:[~2003-05-22 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 6:51 H. J. Lu
2003-05-22 7:03 ` Andreas Jaeger
2003-05-22 7:08 ` H. J. Lu [this message]
2003-05-22 8:34 ` H. J. Lu
2003-05-22 14:43 ` Daniel Berlin
2003-05-22 14:45 ` Andrew Pinski
2003-05-22 14:59 ` H. J. Lu
2003-05-22 18:20 ` Joseph S. Myers
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=20030522000216.A6832@lucon.org \
--to=hjl@lucon.org \
--cc=aj@suse.de \
--cc=dberlin@dberlin.org \
--cc=gcc@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).