Date: Tue, 27 May 2003 20:10:01 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Doug Rabson <dfr@nlsystems.com> Cc: freebsd-current@freebsd.org Subject: Re: gcc/libm floating-point bug? Message-ID: <20030527200208.L1802@gamplex.bde.org> In-Reply-To: <200305270942.42945.dfr@nlsystems.com> References: <200305201025.30296.jlido@goof.com> <20030522093623.30915ed0.fearow@attbi.com> <200305270942.42945.dfr@nlsystems.com>
index | next in thread | previous in thread | raw e-mail
On Tue, 27 May 2003, Doug Rabson wrote: > On Thursday 22 May 2003 6:32 pm, David O'Brien wrote: > > On Thu, May 22, 2003 at 09:36:23AM -0500, Anti wrote: > > > p4 should expand to "-march=pentium4 -mno-sse2" > > > > If we are going to make any change, it should be one we know will > > deal with the issue once and for all. I also considered submitting a > > patch like that, but it is too late in the game to figure out if > > "-march=pentium4 -mno-sse2" would be sufficient in all cases. > > Even for special cases, it is hard to use -msse (or -msse2) with > gcc-3.2.x since it doesn't always manage to 16-byte align the stack > pointer. This makes it hard to declare local vector float variables > safely. All of this appears to be fixed in gcc-3.3-prerelease at least. Isn't this "fixed" in gcc-3.any (gcc-3.2 on i386's at least) except for signal stacks which are partly the kernel's responsibility? gcc-3.2 still pessimizes stack alignment and invites bugs by doing it in functions that don't need it and depending on callers doing it. Brucehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030527200208.L1802>