public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hanwen at xs4all dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/25761] -fpic (not -fPIC) does not work with i686-darwin
Date: Wed, 01 Mar 2006 13:01:00 -0000 [thread overview]
Message-ID: <20060301130129.20933.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25761-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from hanwen at xs4all dot nl 2006-03-01 13:01 -------
Hello,
I also have this problem, but it also gets triggered in the bootstrapping phase
for a cross-compiler.
This is while creating a compiling i686-linux -> i686-apple-darwin8
crosscompiler on Fedora Core 4; I consider this a major bug.
/home/hanwen/vc/gub/target/darwin-x86/src/gcc-4.1.0/libiberty/regex.c: In
function ‘byte_common_op_match_null_string_p’:
/home/hanwen/vc/gub/target/darwin-x86/src/gcc-4.1.0/libiberty/regex.c:7724:
error: unrecognizable insn:
(insn 22 21 23 2
/home/hanwen/vc/gub/target/darwin-x86/src/gcc-4.1.0/libiberty/regex.c:7652 (set
(reg:SI 78)
(label_ref:SI 26)) -1 (nil)
(insn_list:REG_LABEL 26 (nil)))
/home/hanwen/vc/gub/target/darwin-x86/src/gcc-4.1.0/libiberty/regex.c:7724:
internal compiler error: in extract_insn, at recog.c:2084
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
This was triggered by compiling with the following configure flags. If
necessary, I can send a CPP output file.
--prefix=/home/hanwen/vc/gub/target/darwin-x86/install/gcc-root/usr
--program-prefix=i686-apple-darwin8-
--prefix=/home/hanwen/vc/gub/target/darwin-x86/system/usr/cross/
--with-slibdir=/usr/lib/ --target=i686-apple-darwin8
--with-sysroot=/home/hanwen/vc/gub/target/darwin-x86/system/
--with-as=/home/hanwen/vc/gub/target/darwin-x86/system/usr/cross/bin/i686-apple-darwin8-as
--with-ld=/home/hanwen/vc/gub/target/darwin-x86/system/usr/cross/bin/i686-apple-darwin8-ld
--enable-static --enable-shared --enable-languages=c,c++
--enable-libstdcxx-debug
--
hanwen at xs4all dot nl changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hanwen at xs4all dot nl
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25761
next prev parent reply other threads:[~2006-03-01 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 13:31 [Bug target/25761] New: " pinskia at gcc dot gnu dot org
2006-01-12 13:31 ` [Bug target/25761] " pinskia at gcc dot gnu dot org
2006-01-12 16:09 ` pinskia at gcc dot gnu dot org
2006-01-27 16:43 ` pinskia at gcc dot gnu dot org
2006-01-29 16:01 ` pinskia at gcc dot gnu dot org
2006-01-29 16:31 ` pinskia at gcc dot gnu dot org
2006-03-01 13:01 ` hanwen at xs4all dot nl [this message]
2006-03-01 13:39 ` hanwen at xs4all dot nl
2006-03-01 14:10 ` pinskia at gcc dot gnu dot org
2006-03-01 19:14 ` pinskia at gcc dot gnu dot org
2006-03-01 19:28 ` pinskia at gcc dot gnu dot org
2006-03-01 19:28 ` pinskia 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=20060301130129.20933.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).