This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs-1.1 status
- To: law at cygnus dot com, Andi Kleen <ak at muc dot de>
- Subject: Re: egcs-1.1 status
- From: Andi Kleen <ak at muc dot de>
- Date: Fri, 21 Aug 1998 22:38:23 +0200
- Cc: "H.J. Lu" <hjl at lucon dot org>, manfred at s-direktnet dot de, Manfred dot Hollstein at ks dot sel dot alcatel dot de, egcs at cygnus dot com
- References: <19980821221249.A16758@kali.lrz-muenchen.de> <3062.903731094@hurl.cygnus.com>
On Fri, Aug 21, 1998 at 10:24:54PM +0200, Jeffrey A Law wrote:
>
>
> In message <19980821221249.A16758@kali.lrz-muenchen.de>you write:
> > I was refering to 2.1 kernels. There were some fixes in 2.1, but it seems t hey
> > were not enough to make it work in all cases. If you look at
> > include/asm-i386/string.h in a Linux installation you'll see that it is
> > rather hairy asm code, that is why I suggested to replace the non speed
> > critical things with C functions.
> Oh. Someone would have to take a very careful look at them to see
> if they're really correct.
Their main problem is that they use too many registers.
>
> > A new problem that just has appeared today is that Linux 2.1 uses
> > __attribute__((regparm)) for some critical functions, and at least egcs 1.0
> > seems to have problems to generate correct code with this in all cases.
> Oh god. Please stop them from doing this. regparm does not work on
> the x86 and will never work correctly on the x86. They're just going
> to shoot themselves in the foot.
Hmm. Do you think explicitely coding it as an __asm__ would be sufficient
as a workaround?
-Andi