All of lore.kernel.org
 help / color / mirror / Atom feed
From: bame@riverrock.org
To: drepper@cygnus.com (Ulrich Drepper)
Cc: Alan Modra <alan@linuxcare.com.au>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Get rid of %r8 linker stubs
Date: Tue, 04 Jul 2000 19:52:33 -0600	[thread overview]
Message-ID: <m139eMc-001VsnC@chalet> (raw)
In-Reply-To: Your message of "04 Jul 2000 17:57:41 PDT." <m3em591ji2.fsf@otr.mynet.cygnus.com>

= Alan Modra <alan@linuxcare.com.au> writes:
= 
= > The trouble is that _init is a single function that's been split in two
= > (see glibc/csu/Makefile crti,crtn), thus the linker thinks it's quite OK
= > to insert a stub at the start of the second section.  I'll have to do
= > something special with the .init section to work around this problem.
= 
= Simply create an appropriate initfini.c file for HP/UX.  Look in the
= current glibc sources and you'll see that we already do this for SH.

I don't think that'll work, because the parisc linker thinks it's allowed
to insert stubs in between separately-loaded things like functions.  The
use of .init from multiple .o files looks to the linker just like the
use of .text from multiple .o files.  I'd say there's a good chance the
linker might insert stubs *between* individual .init entries too (not
to mention .fini, and in general users can probably create arbitrary
segments to act similarly).

So unless we get to change how .init works (ugly hacks to gas perhaps?
I hope not) I think a special case in the linker is required.  I just
hope there's some sort of attribute on these magic kludge segments which
the linker can use rather than hard-coding the names or something.

Hopefully someone else has a better idea.

	-Paul Bame

  reply	other threads:[~2000-07-05  1:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-04 22:33 [parisc-linux] Get rid of %r8 linker stubs bame
2000-07-05  0:36 ` Alan Modra
2000-07-05  0:57   ` Ulrich Drepper
2000-07-05  1:52     ` bame [this message]
2000-07-05  2:38       ` Alan Modra
2000-07-05  1:55     ` Alan Modra
2000-07-05  2:58   ` bame
2000-07-05  6:43     ` Patric Karlstrom
2000-07-05  6:26       ` willy
  -- strict thread matches above, loose matches on Subject: below --
2000-06-21 14:07 Alan Modra
2000-06-22 20:33 ` Paul Bame
2000-06-22 20:35   ` Jeffrey A Law
2000-06-23  1:45   ` Alan Modra
2000-06-23 10:34     ` Alan Modra
2000-07-03 19:15       ` willy
2000-07-04 14:21     ` willy
2000-07-05  0:38       ` Alan Modra

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=m139eMc-001VsnC@chalet \
    --to=bame@riverrock.org \
    --cc=alan@linuxcare.com.au \
    --cc=drepper@cygnus.com \
    --cc=parisc-linux@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.