Date: Tue, 27 May 2003 08:12:11 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Bruce Evans <bde@zeta.org.au> Cc: freebsd-current@freebsd.org Subject: Re: gcc/libm floating-point bug? Message-ID: <3ED3804B.DC65E10A@mindspring.com> References: <200305201025.30296.jlido@goof.com> <20030522093623.30915ed0.fearow@attbi.com> <20030527200208.L1802@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce Evans wrote: > On Tue, 27 May 2003, Doug Rabson wrote: > > 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. Pretty sure it's still broke, even in 3.3. BTW: signal stacks are irrelevent; technically, you are not allowed to do floating point in signal handlers anyway. 8-). -- Terry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3ED3804B.DC65E10A>