From: Geoffrey KEATING <geoffk@discus.anu.edu.au>
To: hjl@lucon.org (H.J. Lu)
Cc: egcs@cygnus.com, libc-linux@gnu.org (GNU C Library)
Subject: Re: -fpic on ppc with SVR4 ABI
Date: Thu, 16 Oct 1997 21:51:00 -0000 [thread overview]
Message-ID: <199710170220.MAA23405@discus.anu.edu.au> (raw)
In-Reply-To: <m0xLwfP-0004edC@ocean.lucon.org>
> From: hjl@lucon.org (H.J. Lu)
> Date: Thu, 16 Oct 1997 13:37:11 -0700 (PDT)
> When I tried to compile glibc for powerpc using egcs, I got
>
> vfscanf.c: In function `_IO_vfscanf':
> vfscanf.c:1166: internal error--unrecognizable insn:
> (insn 26472 516 506 (set (reg:SI 8 r8)
> (unspec[
> (symbol_ref:SI ("@__ctype_b"))
> (mem:SI (plus:SI (reg:SI 31 r31)
> (const_int 128)))
> ] 8)) -1 (nil)
> (nil))
>
> when making stdio-common/vfscanf.os with -fpic. -fPIC is fine.
> I was wondering if anyone had tried to use egcs to build shared
> libraries on powerpc with -fpic and SVR4 ABI.
>
> BTW, I cannot find a small test case. The one I got is several
> hundred lines.
>
> Thanks.
I have a medium-sized test case somewhere; this particular bug is
triggered by gcc putting the GOT register in memory, which the
.md file can't cope with.
I have a patch for egcs at
< http://discus.anu.edu.au/~geoffk/egcs-geoffk.diff.gz >, which fixes
this and many other bugs. I have another more extensive patch at home
which fixes even more bugs, most notably a bug involving constant
folding on switch statements. The first patch was sent to egcs-bugs
and will eventually end up in the distribution; I'm still testing the
second patch.
I've been told that current binutils don't work either (I use my own
extensively patched version which works fine), and there's a typo in
glibc in sysdeps/powerpc/dl-machine.h ('finaladdr' should be
'finalvalue' or something).
--
Geoff Keating <Geoff.Keating@anu.edu.au>
prev parent reply other threads:[~1997-10-16 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-16 15:19 H.J. Lu
1997-10-16 21:51 ` Geoffrey KEATING [this message]
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=199710170220.MAA23405@discus.anu.edu.au \
--to=geoffk@discus.anu.edu.au \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=libc-linux@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).