From: "Joel Soete" <soete.joel@tiscali.be>
To: "Grant Grundler" <grundler@parisc-linux.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [gcc] should we teach gcc some new tricks?
Date: Thu, 23 Jun 2005 08:10:19 +0200 [thread overview]
Message-ID: <4282FEEE0000FA5F@mail-6-bnl.tiscali.it> (raw)
In-Reply-To: <20050623052753.GA20584@colo.lackof.org>
> -- Original Message --
> Date: Wed, 22 Jun 2005 23:27:53 -0600
> From: Grant Grundler <grundler@parisc-linux.org>
> To: Joel Soete <soete.joel@tiscali.be>
> Cc: parisc-linux@lists.parisc-linux.org
> Subject: Re: [parisc-linux] [gcc] should we teach gcc some new tricks?
>
>
> On Wed, Jun 22, 2005 at 07:54:54PM +0000, Joel Soete wrote:
> > of fp registers?
> > or how may I try to define it as accurately as possible?
> > (I objdump a operating 2.6.12-rc.-pa. 64bit to grep some 'fr[12][0..9=
]'
> and
> > all of them seems to be used?
>
> Of course they will all be used - kernel has to save and restore
> process state when switching context.
Oops I missed it (my bad)
> You have to look at each
> use and determine why FP is being used. There shouldn't
> be that many different uses.
>
Thanks for enlightenment,
I still have to make a lot of progress ;-)
> > Do I have to look elsewhere; tausq also spoke about: sic
> > [...]One proposal that has been talked about before is if we can
> > compile a version of the millicode lib that uses limited fpregs range=
> > and compile the kernel using this new option that Dave is talking abo=
ut,
> > then we will be able to get by using a (much) smaller subset of fp re=
gs
> > and we won't have to save/restore them in the kernel. )
>
> That's correct - but we will still have to save/restore all FP regs
> on a general context switch - just a subset of those when
> entering/leaving the kernel (e.g. handling an external interrupt).
>
Thanks,
Joel
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-06-23 6:10 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 13:07 [parisc-linux] [gcc] should we teach gcc some new tricks? Randolph Chung
2005-03-24 13:27 ` James A. Morrison
2005-03-24 16:19 ` John David Anglin
2005-03-24 16:59 ` Grant Grundler
2005-03-24 17:35 ` John David Anglin
2005-03-24 21:23 ` Grant Grundler
[not found] ` <200503242133.j2OLXl4R020985@hiauly1.hia.nrc.ca>
2005-03-24 22:33 ` Grant Grundler
2005-03-24 23:34 ` John David Anglin
2005-03-24 23:55 ` Randolph Chung
2005-03-24 23:59 ` Randolph Chung
2005-03-25 0:07 ` John David Anglin
2005-06-22 19:54 ` Joel Soete
2005-06-23 3:23 ` John David Anglin
2005-06-23 5:27 ` Grant Grundler
2005-06-23 6:10 ` Joel Soete [this message]
2005-03-24 19:37 ` James A. Morrison
2005-03-24 21:33 ` Grant Grundler
2005-03-26 8:55 ` Matthias Klose
2005-03-26 15:48 ` John David Anglin
2005-03-26 21:35 ` Grant Grundler
[not found] ` <16971.44399.144991.110733@gargle.gargle.HOWL>
2005-03-29 1:36 ` John David Anglin
2005-03-31 12:08 ` Michael S. Zick
2005-05-02 18:37 ` Joel Soete
2005-05-02 19:01 ` John David Anglin
2005-05-02 20:20 ` John David Anglin
2005-05-02 20:46 ` John David Anglin
2005-05-05 16:20 ` Joel Soete
2005-05-05 17:07 ` John David Anglin
2005-05-05 18:41 ` Joel Soete
[not found] <200505031334.j43DYRBT004104@hiauly1.hia.nrc.ca>
2005-05-03 17:58 ` Joel Soete
2005-05-03 19:00 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
2005-06-23 7:19 Joel Soete
2005-06-23 13:09 ` John David Anglin
[not found] <42B91C1400000F85@mail-1-bnl.tiscali.it>
2005-06-25 6:46 ` John David Anglin
2005-06-25 8:29 ` Joel Soete
2005-07-01 13:43 ` Joel Soete
[not found] <42C81991.6030502@tiscali.be>
2005-07-03 18:47 ` John David Anglin
2005-07-04 14:51 ` Joel Soete
2005-07-05 14:59 ` Joel Soete
2005-07-07 1:27 ` John David Anglin
[not found] <200507051816.j65IGuIY028621@hiauly1.hia.nrc.ca>
2005-07-06 16:40 ` Joel Soete
2005-07-06 17:00 ` John David Anglin
[not found] <42B91C1400005075@mail-1-bnl.tiscali.it>
2005-07-09 15:42 ` Joel Soete
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=4282FEEE0000FA5F@mail-6-bnl.tiscali.it \
--to=soete.joel@tiscali.be \
--cc=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.org \
/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