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: Wed, 03 Jan 2001 21:04:25 -0700 [thread overview]
Message-ID: <8186.978581065@upchuck> (raw)
In-Reply-To: Your message of Wed, 03 Jan 2001 15:44:58 +1100. <Pine.LNX.4.21.0101031532370.24351-100000@front.linuxcare.com.au>
In message <Pine.LNX.4.21.0101031532370.24351-100000@front.linuxcare.com.au>y
> I'm not particularly enthusiastic about the idea either. It seemed to be
> the best solution in the face of a number of packages that "know" libgcc
> isn't needed when linking certain programs. eg. linux kernel, binutils
> testsuite. The alternatives are
> a) fix all the affected packages
> b) modify linker scripts
> c) magic inbuilt linker behaviour.
But I would consider those very special cases and wouldn't want to pollute
the linker to work around those special cases.
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
small price given that the only ones you probably call with any
regularity are div/mod in which case the cost of reloading the pic
registers is dwarfed by cost of the divide.
Then for the kernel you just put the needed routines (probably just
$$div, $$divU, $$rem, $$remU) into arch/parisc/support.S.
jeff
next prev parent reply other threads:[~2001-01-04 4:54 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 [this message]
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
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=8186.978581065@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.