Linux PARISC architecture development
 help / color / mirror / Atom feed
From: David Huggins-Daines <dhd@linuxcare.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: parisc-linux@thepuffingroup.com, parisc@lists.linuxcare.com
Subject: Re: Incompatibility of PIC and non-PIC
Date: 18 Aug 2000 13:25:53 -0400	[thread overview]
Message-ID: <8766oy1nxa.fsf@linuxcare.com> (raw)
In-Reply-To: Alan Modra's message of "Sat, 19 Aug 2000 00:29:01 +1000 (EST)"

Alan Modra <alan@linuxcare.com.au> writes:

> On Fri, 18 Aug 2000, Alan Modra wrote:
> 
> > One way to keep out current ABI is to generate a .plt and import stubs
> > when statically linking PIC code.  That should be relatively easy to do in
> > the linker.
> 
> A bit of head-scratching, a couple of added functions, and the linker now
> detects PIC functions and handles them appropriately.

Sorry to burst your bubble but this doesn't work in the real world,
where "real world" is defined as 'hppa-linux-gcc -o hello hello.c'

In fact this new linker ends up marking basically everything as
potentially PIC, creating unnecessary import stubs for most functions
in libc.a, and *not* actually switching the relocations to point to
import stubs in the case where I am actually calling PIC in libgcc.a.

Oh and it segfaults on undefined weak symbols though that's easily
fixed.

I'm not even sure where to start fixing this.  I guess I'll try to
find something else to do today :(

-- 
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.

  reply	other threads:[~2000-08-18 17:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-17 22:25 [parisc-linux] Incompatibility of PIC and non-PIC David Huggins-Daines
2000-08-18  0:12 ` Alan Modra
2000-08-18 14:29   ` Alan Modra
2000-08-18 17:25     ` David Huggins-Daines [this message]
2000-08-18 20:14       ` David Huggins-Daines
2000-08-18 23:35         ` Alan Modra
2000-08-19  5:29         ` Alan Modra
2000-08-21 17:46           ` David Huggins-Daines
2000-08-21 19:09             ` David Huggins-Daines
2000-08-21 23:39               ` Alan Modra
2000-08-19 22:00         ` David Huggins-Daines
2000-08-20  3:07           ` Alan Modra
2000-08-20  2:43             ` Matthew Wilcox
2000-08-20  4:19               ` Alan Modra
2000-08-21 13:41                 ` David Huggins-Daines
2000-08-21 13:38             ` David Huggins-Daines
     [not found] <alan@linuxcare.com.au>
2000-08-23  8:49 ` Tor Arntsen
2000-08-23  9:49   ` Alan Modra
  -- strict thread matches above, loose matches on Subject: below --
2000-08-23 10:31 Tor Arntsen
2000-08-23 10:46 ` Alan Modra
2000-08-23 11:26 Tor Arntsen
2000-08-23 13:51 ` Matthew Wilcox

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=8766oy1nxa.fsf@linuxcare.com \
    --to=dhd@linuxcare.com \
    --cc=alan@linuxcare.com.au \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=parisc@lists.linuxcare.com \
    /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