Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: bame@riverrock.org, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Get rid of %r8 linker stubs
Date: 04 Jul 2000 17:57:41 -0700	[thread overview]
Message-ID: <m3em591ji2.fsf@otr.mynet.cygnus.com> (raw)
In-Reply-To: Alan Modra's message of "Wed, 5 Jul 2000 10:36:07 +1000 (EST)"

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.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------

  reply	other threads:[~2000-07-05  0:56 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 [this message]
2000-07-05  1:52     ` bame
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=m3em591ji2.fsf@otr.mynet.cygnus.com \
    --to=drepper@redhat.com \
    --cc=alan@linuxcare.com.au \
    --cc=bame@riverrock.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox