From: Jeffrey A Law <law@redhat.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: Paul Bame <bame@fc.hp.com>,
John David Anglin <dave@hiauly1.hia.nrc.ca>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] where to put 64 bit libmilli?
Date: Thu, 04 Jan 2001 10:37:20 -0700 [thread overview]
Message-ID: <11763.978629840@upchuck> (raw)
In-Reply-To: Your message of Thu, 04 Jan 2001 16:20:37 +1100. <Pine.LNX.4.21.0101041608490.15554-100000@front.linuxcare.com.au>
In message <Pine.LNX.4.21.0101041608490.15554-100000@front.linuxcare.com.au>y
ou write:
> On Wed, 3 Jan 2001, Jeffrey A Law wrote:
>
> > The easiest (to me) solution is to put the routines into the system C
> > library. You'd drop the special millcode conventions, but that's a
>
> How about $$dyncall? Wouldn't loading r19/r29 break this function? I'm
> thinking of the case where $$dyncall is passed the address of a local
> function rather than a plabel. We wouldn't want to load r19/r29 with the
> value for a shared libgcc.
$$dyncall is only used for PA32 -- what ABI are you using for PA32? The
existing ones don't require $dp or $gp to be loaded by the caller -- they're
handled in the stub between the caller & callee.
jeff
next prev parent reply other threads:[~2001-01-04 17:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 19:25 [parisc-linux] where to put 64 bit libmilli? Paul Bame
2001-01-02 19:39 ` John David Anglin
2001-01-02 19:58 ` Paul Bame
2001-01-02 20:17 ` Jeffrey A Law
2001-01-03 1:46 ` Alan Modra
2001-01-03 1:57 ` Matthew Wilcox
2001-01-03 2:34 ` Alan Modra
2001-01-03 3:37 ` Jeffrey A Law
2001-01-03 4:11 ` Alan Modra
2001-01-03 4:15 ` Jeffrey A Law
2001-01-03 4:44 ` Alan Modra
2001-01-04 4:04 ` Jeffrey A Law
2001-01-04 5:20 ` Alan Modra
2001-01-04 6:18 ` John David Anglin
2001-01-04 7:03 ` Alan Modra
2001-01-04 16:36 ` Paul Bame
2001-01-04 17:06 ` Jeffrey A Law
2001-01-04 17:29 ` Jeffrey A Law
2001-01-04 17:37 ` Jeffrey A Law [this message]
2001-01-04 17:41 ` Paul Bame
2001-01-04 23:52 ` Alan Modra
-- strict thread matches above, loose matches on Subject: below --
2001-01-04 19:00 Cary Coutant
2001-01-04 19:15 ` Grant Grundler
2001-01-04 21:20 Cary Coutant
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=11763.978629840@upchuck \
--to=law@redhat.com \
--cc=alan@linuxcare.com.au \
--cc=bame@fc.hp.com \
--cc=dave@hiauly1.hia.nrc.ca \
--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.