public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/16109] error: architecture mismatch on "fzero".
Date: Thu, 08 Jul 2004 18:15:00 -0000 [thread overview]
Message-ID: <20040708181535.1127.qmail@sourceware.org> (raw)
In-Reply-To: <20040621084809.16109.pluto@pld-linux.org>
------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-07-08 18:15 -------
> (It could come from a --with-cpu=v9 on the configure line, but I don't see it
> in the output of 'gcc -v'.
It is actually automatically set by the configure script:
sparc*-*-*)
# Some standard aliases.
case x$with_cpu in
xsparc)
with_cpu=v7
;;
xsparc86x)
with_cpu=sparclite86x
;;
xsparcv9 | xsparc64)
with_cpu=v9
;;
esac
Jakub, how is your sparc64-redhat-linux compiler supposed to work? I see you
configured it with --with-cpu=v7, so the driver will append -mcpu=v7 to the
command line if there is no -mcpu, right? How do you turn that into
-mcpu=ultrasparc?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16109
next prev parent reply other threads:[~2004-07-08 18:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 8:48 [Bug other/16109] New: " pluto at pld-linux dot org
2004-06-21 9:09 ` [Bug target/16109] " ebotcazou at gcc dot gnu dot org
2004-06-21 9:16 ` pluto at pld-linux dot org
2004-06-21 9:37 ` ebotcazou at gcc dot gnu dot org
2004-06-21 9:40 ` pluto at pld-linux dot org
2004-06-21 9:50 ` ebotcazou at gcc dot gnu dot org
2004-06-21 10:59 ` pluto at pld-linux dot org
2004-06-21 11:22 ` pluto at pld-linux dot org
2004-06-21 14:17 ` ebotcazou at gcc dot gnu dot org
2004-06-21 14:38 ` jakub at gcc dot gnu dot org
2004-07-07 13:47 ` ebotcazou at gcc dot gnu dot org
2004-07-07 14:01 ` jakub at gcc dot gnu dot org
2004-07-07 14:40 ` ebotcazou at gcc dot gnu dot org
2004-07-08 18:15 ` ebotcazou at gcc dot gnu dot org [this message]
2004-07-08 18:27 ` jakub at gcc dot gnu dot org
2004-07-08 19:28 ` ebotcazou at gcc dot gnu dot org
2004-07-10 20:31 ` ebotcazou at gcc dot gnu dot org
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=20040708181535.1127.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).