public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Golubev I. N." <gin@mo.msk.ru> To: gcc-gnats@gcc.gnu.org Subject: bootstrap/3460: broken libgcc2 -fPIC Date: Thu, 28 Jun 2001 07:06:00 -0000 [thread overview] Message-ID: <02473b3b381b35-gin@mo.msk.ru> (raw) >Number: 3460 >Category: bootstrap >Synopsis: broken libgcc2 -fPIC >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Thu Jun 28 07:06:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Golubev I. N. >Release: 3.0 >Organization: >Environment: System: SCO_SV d-fens 3.2 2 i386 host: i586-pc-sco3.2v5.0.2 build: i586-pc-sco3.2v5.0.2 target: i586-pc-sco3.2v5.0.2 configured with: : (reconfigured) : (reconfigured) ../gcc-3.0/configure --without-included-gettext --prefix=/usr --with-as=/usr/bin/gas --enable-multilib --disable-static --enable-shared --with-system-zlib --program-transform-name=s/cpp/gcpp/ >Description: 1) Settings of `MULTILIB_*' in `t-sco5gas' (version as in < http://gcc.gnu.org/cgi-bin/cvsweb.cgi/~checkout~/gcc/gcc/config/i386/t-sco5gas?rev=1.3&content-type=text/plain >) affect nothing. In particular, they do not cause `stmp-multilib' make procedure to put `-fPIC' in ${LIBGCC2_CFLAGS}. This explains why what is described below was never hit. 2) gcc generates incorrect asm code when compiling `unwind-dw2.c' for target `libgcc2.a' with ${TARGET_LIBGCC2_CFLAGS} containing `-fPIC' as in `t-sco5'. It causes `gas' from binutils-2.11 to complain: 1.s:2948: Error: Rest of line ignored. First ignored character is `@'. for gcc output: .long .LFB1@GOTOFF Configuring gcc with native as has even less chances to work. It generated inacceptable code at least in 2.95.2, and I always configure it with gnu as since then. >How-To-Repeat: make bootstrap >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-06-28 7:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-28 7:06 Golubev I. N. [this message] 2001-07-05 13:29 rth
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=02473b3b381b35-gin@mo.msk.ru \ --to=gin@mo.msk.ru \ --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: linkBe 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).