Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 01 Feb 2011 10:07:15 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        freebsd-toolchain@freebsd.org
Subject:   Re: [toolchain] ${CC} in share/mk/bsd.cpu.mk
Message-ID:  <4D483DC3.9000506@bsdimp.com>
In-Reply-To: <AANLkTikNbApV_1N1PSEo-_wkP7t821dMAoVPEcETWLKR@mail.gmail.com>
References:  <AANLkTikNbApV_1N1PSEo-_wkP7t821dMAoVPEcETWLKR@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 02/01/2011 04:27, b. f. wrote:
> Gerald Pfeifer wrote:
>> On Sun, 30 Jan 2011, Alexander Best wrote:
>>> i might have described things a bit too complicated. basically i want to
>>> have CPUTYPE ?= core2 in my make.conf. clang is capable of producing
>>> core2 specific code, however core2 always gets downgraded by
>>> share/mk/bsd.cpu.mk to nocona in order not to confuse gcc.
>>>
>>> any chance of fixing this?
>> I guess one of those extern compilers Robert has in mind should
>> be lang/gcc46 from the Ports Collection which is perfectly happy
>> to generate core2 code.  I agree we need good infrastructure to
>> support such cases.
>
> Related:
>
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=conf/84800
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=conf/112997
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=conf/30399
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=i386/122623
>
> The longevity of some of these is remarkable.

Wow!  I think the fortran one takes the cake for ancientness :)  When 
applying it, keep in mind that we do things a little differently...  
Maybe I'll take a look at it/them :)

Warner




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D483DC3.9000506>