From: "Timothy J. Wood" <tjw@omnigroup.com>
To: gcc@gcc.gnu.org
Subject: 3.4 bootstrap failure on powerpc-apple-darwin7.2.0
Date: Sun, 18 Jan 2004 04:39:00 -0000 [thread overview]
Message-ID: <4D4D1AE6-4970-11D8-8B22-0003933F3BC2@omnigroup.com> (raw)
../gcc/configure --prefix="$PREFIX" --enable-altivec
--enable-languages="c,c++,objc"
make
/Users/bungi/Source/GNU/gcc/gcc-3.4/build/gcc/xgcc
-B/Users/bungi/Source/GNU/gcc/gcc-3.4/build/gcc/
-B/Users/bungi/Source/GNU/gcc/gcc-3.4/install/powerpc-apple-
darwin7.2.0/bin/
-B/Users/bungi/Source/GNU/gcc/gcc-3.4/install/powerpc-apple-
darwin7.2.0/lib/ -isystem
/Users/bungi/Source/GNU/gcc/gcc-3.4/install/powerpc-apple-darwin7.2.0/
include -isystem
/Users/bungi/Source/GNU/gcc/gcc-3.4/install/powerpc-apple-darwin7.2.0/
sys-include -O2 -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include -mlong-double-128 -g -DHAVE_GTHR_DEFAULT
-DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I -I../../gcc/gcc
-I../../gcc/gcc/ -I../../gcc/gcc/../include -I../intl -fexceptions -c
../../gcc/gcc/unwind-dw2.c -o libgcc/./unwind-dw2.o
/var/tmp//ccec9Kuq.s:4837:stvx vector instruction is optional for the
PowerPC (not allowed without -force_cpusubtype_ALL option)
/var/tmp//ccec9Kuq.s:4840:stvx vector instruction is optional for the
PowerPC (not allowed without -force_cpusubtype_ALL option)
/var/tmp//ccec9Kuq.s:4843:stvx vector instruction is optional for the
PowerPC (not allowed without -force_cpusubtype_ALL option)
/var/tmp//ccec9Kuq.s:4846:stvx vector instruction is optional for the
PowerPC (not allowed without -force_cpusubtype_ALL option)
...
Am I supposed to do something to get '-force_cpusubtype_ALL' (or
maybe -faltivec) passed to xgcc when bootstrapping, or is this an
actual bug?
-tim
next reply other threads:[~2004-01-18 4:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 4:39 Timothy J. Wood [this message]
2004-01-18 16:07 ` Andrew Pinski
2004-01-18 19:27 ` Timothy J. Wood
2004-01-18 23:11 ` Ziemowit Laski
2004-01-18 23:18 ` Andrew Pinski
2004-01-18 23:36 ` Ziemowit Laski
2004-01-18 23:45 ` Andrew Pinski
2004-01-21 14:56 ` Segher Boessenkool
2004-01-19 20:57 ` Dale Johannesen
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=4D4D1AE6-4970-11D8-8B22-0003933F3BC2@omnigroup.com \
--to=tjw@omnigroup.com \
--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).