Date: Tue, 20 May 2003 20:42:34 +0200 From: Morten Rodal <morten@rodal.no> To: Terry Lambert <tlambert2@mindspring.com>, Jon Lido <jlido@goof.com>, freebsd-current@freebsd.org Subject: Re: gcc/libm floating-point bug? Message-ID: <20030520184234.GE530@atlantis.rodal.no> In-Reply-To: <20030520180336.GB2372@HAL9000.homeunix.com> References: <200305201025.30296.jlido@goof.com> <3ECA526F.A6E4A085@mindspring.com> <20030520180336.GB2372@HAL9000.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--9UV9rz0O2dU/yYYn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 20, 2003 at 11:03:36AM -0700, David Schultz wrote: > That's for an Alpha-specific problem. The i386-specific problem > is due to a bug gcc has that involves Pentium 4 code generation > and aliasing. The latter can be fixed by removing > -march=3Dpentium4, disabling optimization, or upgrading to gcc 3.3. > The former is intentional and not expected to change; gcc > generates non-standard FP math code on Alpha because it saves a > few instructions to deal with NaNs, etc. We work around it by > setting -mieee in bsd.cpu.mk for Alpha. > The upgrade from gcc 3.2 to 3.3 isn't scheduled before after 5.1 is released? (I think I saw some post about that someplace) --=20 Morten Rodal --9UV9rz0O2dU/yYYn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+yncabWe1Cy11WVsRAt4TAJ91MrB/SPfr5yx2pUQM9vbduufRHgCfeSOO 3opZpAVQMwAiOa2s0CRHdOQ= =t5H5 -----END PGP SIGNATURE----- --9UV9rz0O2dU/yYYn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030520184234.GE530>