Date: Thu, 7 Feb 2002 19:39:36 +0100 From: Wilko Bulte <wkb@freebie.xs4all.nl> To: "David O'Brien" <obrien@FreeBSD.ORG> Cc: current@FreeBSD.ORG Subject: Re: How about gcj? (Re: Not committing WARNS settings...) Message-ID: <20020207193936.C19376@freebie.xs4all.nl> In-Reply-To: <20020207103541.D53237@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Thu, Feb 07, 2002 at 10:35:41AM -0800 References: <20020206192238.B3347@dragon.nuxi.com> <200202070539.g175dbQ22609@aldan.algebra.com> <20020207101133.B53237@dragon.nuxi.com> <20020207192957.B19376@freebie.xs4all.nl> <20020207103541.D53237@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 07, 2002 at 10:35:41AM -0800, David O'Brien wrote: > On Thu, Feb 07, 2002 at 07:29:57PM +0100, Wilko Bulte wrote: > > - is GCC3 also better on Alpha as far as correctness of the generated > > code goes? Or is that what you mean by "bad optimised code" ? > > We shall see. OK. 8-) > > - The gcc 2.95 compiler is quite a bit slower (it appears) on Alpha than > > on x86. Do you have any idea how gcc3 does in this respect? > > 3.1 will also be slower on the Alpha. It is really an issue of the code > generator. Generating x86 code on an Alpha is faster than generating > [native] Alpha code. The Alpha code generator is slow. It may be that > all 64 bit or RISC GCC code generation is slow -- we will see soon for > the sparc64. Thanks. So it is the code generator itself, I always thought it would be the optimiser that needs more time to do a decent job on a RISC. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020207193936.C19376>