public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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: Mon, 21 Jun 2004 14:38:00 -0000 [thread overview]
Message-ID: <20040621143809.15887.qmail@sourceware.org> (raw)
In-Reply-To: <20040621084809.16109.pluto@pld-linux.org>
------- Additional Comments From jakub at gcc dot gnu dot org 2004-06-21 14:38 -------
I don't think so. GCC on sparc64-*-linux is supposed to default to
-mcpu=ultrasparc if no -mcpu= is given.
> a.c; gcc34 -m64 -c -O2 a.c -v
Reading specs from /usr/lib/gcc/sparc64-redhat-linux/3.4.0/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-languages=c,c++,objc,java,f77
--host=sparc64-redhat-linux --build=sparc64-redhat-linux
--target=sparc64-redhat-linux --with-cpu=v7
Thread model: posix
gcc version 3.4.0 (Red Hat Linux 3.4.0-1.sparc)
/usr/libexec/gcc/sparc64-redhat-linux/3.4.0/cc1 -quiet -v -D__arch64__ a.c
-mptr64 -mstack-bias -mlong-double-128 -mcpu=ultrasparc -mvis -quiet -dumpbase
a.c -m64 -auxbase a -O2 -version -o /tmp/cctmL5p8.s
ignoring nonexistent directory
"/usr/lib/gcc/sparc64-redhat-linux/3.4.0/../../../../sparc64-redhat-linux/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include
/usr/lib/gcc/sparc64-redhat-linux/3.4.0/include
/usr/include
End of search list.
GNU C version 3.4.0 (Red Hat Linux 3.4.0-1.sparc) (sparc64-redhat-linux)
compiled by GNU C version 3.4.0 (Red Hat Linux 3.4.0-1.sparc).
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
as -V -Qy -s -Av9a -64 -no-undeclared-regs -relax -o a.o /tmp/cctmL5p8.s
GNU assembler version 2.15.90.0.3 (sparc-redhat-linux) using BFD version
2.15.90.0.3 20040415
There used to be a bug in this area, but it should be fixed by my:
* config/sparc/linux64.h (OPTION_DEFAULT_SPECS): If SPARC_BI_ARCH,
override sparc.h definition.
patch.
asm_cpu_default is supposed to be used, because no -mcpu=* nor one of its
obsolete variants are used.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16109
next prev parent reply other threads:[~2004-06-21 14:38 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 [this message]
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
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=20040621143809.15887.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).