This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: State of m68k float emulation in lb1sf68.asm (muldf, divdf)
- From: Jim Wilson <wilson at specifixinc dot com>
- To: tm_gccmail at kloo dot net
- Cc: Pavel Pisa <pisa at cmp dot felk dot cvut dot cz>, gcc at gcc dot gnu dot org
- Date: 17 Nov 2003 12:49:42 -0800
- Subject: Re: State of m68k float emulation in lb1sf68.asm (muldf, divdf)
- References: <Pine.LNX.4.21.0311171149230.26515-100000@mail.kloo.net>
On Mon, 2003-11-17 at 12:11, tm_gccmail@kloo.net wrote:
> The gcc SH port uses fp-bit.c, and I have many users bitterly complaining
> that the gcc SH floating point is slow compared to the Renesas compiler.
You are confusing the issues here. We were talking about lb1sf68.asm,
and this isn't a relevant comment.
I agree that fp-bit.c is not as fast as it could be, I already said that
in an earlier message. I also pointed out ways to fix this. But none
of this is relevent to the lb1sf68.asm issue that this thread was
discussing.
> GMP would still be compiled with gcc, so it's utterly dependent on the gcc
> m68k codegen quality. When I was doing the sun3-linux port, I looked at
> a lot of gcc-m68k output, and I recall not being very impressed with it.
I think you fail to understand how GMP works. Also, I think you
underestimate how good of a m68k compiler gcc is. And this is yet a
different issue than the one we started talking about.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com