Re: System libc++ isn't fully compatible with clang 3.4 from por
--Apple-Mail=_2A25FAD7-165D-4DAC-93DC-B3F4502F7543
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=us-ascii
On 29 Jan 2014, at 15:45, Dmitry Marakasov <amdmi3@amdmi3.ru> wrote:
> * Dimitry Andric (dim@FreeBSD.org) wrote:
>
>>> JFYI, I've just ran into shortcoming of libc++ from 10-RELEASE when used
>>> with clang 3.4 from ports:
>> ...
>>> The cause: http://llvm.org/bugs/show_bug.cgi?id=17798, was fixed in
>>> libc++ r194154. We probably need to update libc++ or at least backport
>>> this into stable branches if we want to support clang 3.4 in ports.
>>
>> Hm, which port is having problems with this? I have built quite a large
>> set, and never encountered this issue.
>>
>> In any case: yes, it is quite long overdue for a libc++ update. :-) I
>> will have a look tonight.
>
> New version of games/spring (not in ports yet).
>
> std::function and lambdas are not that widely used for this problem to
> be common, but some time we may run into it for some critical software.
Okay, I imported the 3.4 version of libc++, which includes the fix for
llvm PR17798, in r261283. I also bumped __FreeBSD_version to 1100007
for it.
-Dimitry
--Apple-Mail=_2A25FAD7-165D-4DAC-93DC-B3F4502F7543
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
iEYEARECAAYFAlLq3h0ACgkQsF6jCi4glqNmdgCg/YE+BtwOfqjzXK0NHluvFPUn
RQEAn0gmmwjcbvZmTEJ6Y74hTpDu+CSH
=5YuX
-----END PGP SIGNATURE-----
--Apple-Mail=_2A25FAD7-165D-4DAC-93DC-B3F4502F7543--
討論串 (同標題文章)
完整討論串 (本文為第 3 之 3 篇)：