Date: Thu, 22 May 2003 09:36:23 -0500 From: Anti <fearow@attbi.com> To: freebsd-current@freebsd.org Subject: Re: gcc/libm floating-point bug? Message-ID: <20030522093623.30915ed0.fearow@attbi.com> In-Reply-To: <200305221010.59718.jlido@goof.com> References: <200305201025.30296.jlido@goof.com> <200305201512.27174.jlido@goof.com> <20030522011014.GC27806@dragon.nuxi.com> <200305221010.59718.jlido@goof.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I feel some will screem if we take away the ability to use > > -march=pentium4 in places they know for sure will work. Unix is about > > mechanisms, not policy. > > Well, we've got a compiler here with a broken mechanism. Deciding whether or > not to act on it sounds like a policy decision to me. I just hope 5.1 > doesn't get shipped with such an easy way to break stuff. p4 should expand to "-march=pentium4 -mno-sse2" (could set it to pentium3, but then people would see pentium3 being used when they specified p4 and think it's a bug)... any educated person with a legit reason to use -march=pentium4 without disabling sse2 can always add it to CFLAGS instead of setting it in CPUTYPE... don't see why anyone wouldn't want to put an end to all the breakage and bug reports due to this when the fix is so simple and of no real harm...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030522093623.30915ed0.fearow>