Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Apr 2012 12:42:37 +0200
From:      Dimitry Andric <dim@FreeBSD.org>
To:        Alexander Best <arundel@freebsd.org>
Cc:        svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org
Subject:   Re: svn commit: r234353 - in head: . contrib/llvm contrib/llvm/include/llvm contrib/llvm/include/llvm-c contrib/llvm/include/llvm-c/Transforms contrib/llvm/include/llvm/ADT contrib/llvm/include/llvm/An...
Message-ID:  <4F928F1D.2080406@FreeBSD.org>
In-Reply-To: <20120419211441.GA7744@freebsd.org>
References:  <201204162123.q3GLNSr6051133@svn.freebsd.org> <20120419211441.GA7744@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2012-04-19 23:14, Alexander Best wrote:
> On Mon Apr 16 12, Dimitry Andric wrote:
>> Author: dim
>> Date: Mon Apr 16 21:23:25 2012
>> New Revision: 234353
>> URL: http://svn.freebsd.org/changeset/base/234353
>>
>> Log:
>>    Upgrade our copy of llvm/clang to trunk r154661, in preparation of the
>>    upcoming 3.1 release (expected in a few weeks).  Preliminary release
>>    notes can be found at:<http://llvm.org/docs/ReleaseNotes.html>;
>
> very nice. :)
>
> any reason '-fformat-extensions'-support still hasn't been pushed upstream as
> something like '-fbsd-extensions'?

Simply ENOTIME.  The support as it is now, is not really acceptable for
upstream, because it is rather a quick 'n dirty hack. :)

Besides, llvm/clang 3.1 has branched for release, and only serious bugs
will be fixed in there, from now on.  So even if I got something whipped
up right now, it would probably not make it in.



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