public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: joel@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/3589: GCC 3.0-CVS illegal instruction on hppa1.1-proelf
Date: Fri, 06 Jul 2001 06:46:00 -0000 [thread overview]
Message-ID: <20010706134341.8060.qmail@sourceware.cygnus.com> (raw)
>Number: 3589
>Category: bootstrap
>Synopsis: GCC 3.0-CVS illegal instruction on hppa1.1-proelf
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jul 06 06:46:04 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: joel@gcc.gnu.org
>Release: gcc 3.0-CVS
>Organization:
>Environment:
GNU/Linux x86 (RedHat 6.2) with binutils 2.11.2 for target
>Description:
Fails with following messages
/usr3/ftp_archive/gnu/gcc/ss/b3/b-hppa1.1-proelf/gcc/xgcc -B/usr3/ftp_archive/gnu/gcc/ss/b3/b-hppa1.1-proelf/gcc/ -nostdinc -B/usr3/ftp_archive/gnu/gcc/ss/b3/b-hppa1.1-proelf/hppa1.1-proelf/newlib/ -isystem /usr3/ftp_archive/gnu/gcc/ss/b3/b-hppa1.1-proelf/hppa1.1-proelf/newlib/targ-include -isystem /usr3/ftp_archive/gnu/gcc/ss/b3/gcc/newlib/libc/include -B/opt/gnucross/hppa1.1-proelf/bin/ -B/opt/gnucross/hppa1.1-proelf/lib/ -isystem /opt/gnucross/hppa1.1-proelf/include -O2 -DCROSS_COMPILE -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include -xassembler-with-cpp -c lib2funcs.asm -o libgcc/./lib2funcs.o
lib2funcs.asm: Assembler messages:
lib2funcs.asm:32: Error: Unknown pseudo-op: `.subspa'
lib2funcs.asm:33: Error: Unknown pseudo-op: `.subspa'
lib2funcs.asm:35: Error: Unknown pseudo-op: `.subspa'
lib2funcs.asm:36: Error: Unknown pseudo-op: `.subspa'
lib2funcs.asm:37: Error: Unknown pseudo-op: `.subspa'
lib2funcs.asm:41: Error: Unknown pseudo-op: `.subspa'
make[2]: *** [libgcc/./lib2funcs.o] Error 1
make[2]: Leaving directory `/usr3/ftp_archive/gnu/gcc/ss/b3/b-hppa1.1-proelf/gcc'
make[1]: *** [libgcc.a] Error 2
>How-To-Repeat:
Configure and build as follows:
../gcc/configure --target=${1} \
--with-gnu-as --with-gnu-ld --with-newlib --verbose \
--prefix=/opt/gnucross '--enable-languages=c,c++' && make
Contact me for assistance with binutils.
>Fix:
Unknown.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-07-06 6:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 6:46 joel [this message]
2002-03-22 9:41 vmakarov
2002-03-25 8:26 Vladimir Makarov
2002-03-25 10:16 law
2002-03-25 10:26 Vladimir Makarov
2002-03-26 6:26 Joel Sherrill
2002-03-26 9:16 Vladimir Makarov
2002-03-26 9:26 Joel Sherrill
2002-03-26 9:36 Vladimir Makarov
2002-03-26 9:56 Vladimir Makarov
2002-03-26 9:56 law
2002-03-26 10:16 Joel Sherrill
2002-03-26 12:56 Vladimir Makarov
2002-03-26 13:06 Joel Sherrill
2002-03-26 13:16 Vladimir Makarov
2002-03-26 13:36 Joel Sherrill
2002-03-26 14:26 Joel Sherrill
2002-03-26 14:26 Vladimir Makarov
2002-03-26 20:06 law
2002-03-27 10:56 Vladimir Makarov
2002-03-28 12:56 Vladimir Makarov
2002-03-28 13:46 John David Anglin
2002-04-01 14:54 vmakarov
2002-06-24 9:11 joel
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=20010706134341.8060.qmail@sourceware.cygnus.com \
--to=joel@gcc.gnu.org \
--cc=gcc-gnats@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).