Date: 22 May 2003 10:25:43 -0700 From: Eric Anholt <eta@lclark.edu> To: Anti <fearow@attbi.com> Cc: freebsd-current@freebsd.org Subject: Re: gcc/libm floating-point bug? Message-ID: <1053624343.664.62.camel@leguin> In-Reply-To: <20030522093623.30915ed0.fearow@attbi.com> References: <200305201025.30296.jlido@goof.com> <200305201512.27174.jlido@goof.com> <20030522011014.GC27806@dragon.nuxi.com> <200305221010.59718.jlido@goof.com> <20030522093623.30915ed0.fearow@attbi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2003-05-22 at 07:36, Anti wrote: > > > 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... As of this morning, p4 CPUTYPE will to produce -march=pentium3. Your solution may have been more correct, but this is just a workaround until the next gcc gets imported. I hope the note in bsd.cpu.mk will be enough to warn people. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1053624343.664.62.camel>