Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Mar 2016 00:16:48 +0100
From:      Dimitry Andric <dim@FreeBSD.org>
To:        Bryan Drewery <bdrewery@FreeBSD.org>
Cc:        toolchain@FreeBSD.org
Subject:   Re: CXXSTD=c++11
Message-ID:  <DE6BC456-3949-4DEF-A8AC-3996680FA0EA@FreeBSD.org>
In-Reply-To: <7B77010A-B377-4B1A-835A-D48F59E5290D@FreeBSD.org>
References:  <56F46BE0.7080909@FreeBSD.org> <43ABA5F3-60E0-4A29-9698-B345A3DA0A8B@FreeBSD.org> <56F46E1B.4010605@FreeBSD.org> <56F46F67.2000807@FreeBSD.org> <7B77010A-B377-4B1A-835A-D48F59E5290D@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail=_6F95CD35-22A5-4E07-9FD0-89ABF4FF74A8
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=windows-1252

On 24 Mar 2016, at 23:54, Dimitry Andric <dim@FreeBSD.org> wrote:
> 
> On 24 Mar 2016, at 23:51, Bryan Drewery <bdrewery@FreeBSD.org> wrote:
...
>> It fails without -std=c++11 (there's more discussion in that link and in
>> PR 205453).
> 
> Yeah, I also commented on PR 205453 in the past, but I still don't
> understand where the external gcc gets its _Static_assert macro from.
> Or whether it gets it at all.  Maybe we should place a hack for this in
> sys/cdefs.h?  We shouldn't litter contrib code with #ifdef GCC_VERSION
> blocks.

Hm, hacking around in cdefs.h also doesn't really help, because gcc
refuses to recognize either _Static_assert or static_assert when it's
not in C++11 mode.  Reading back https://reviews.freebsd.org/D1390, I
see that I originally wanted to avoid building libcxxrt with -std=c++11.
This was so you could even build it with gcc 4.2.1 from base.

However, it really doesn't make much sense to do so, and upstream
libcxxrt simply uses static_assert directly, and requires -std=c++11.  I
will update the libcxxrt build to do so, probably tomorrow.

-Dimitry


--Apple-Mail=_6F95CD35-22A5-4E07-9FD0-89ABF4FF74A8
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.29

iEYEARECAAYFAlb0dXIACgkQsF6jCi4glqOhuwCfZ1ezyu4FcS1tWRqOA1G/evMP
nisAoO38mEZwNhA/aKPELbglsmcuBPY2
=N3SJ
-----END PGP SIGNATURE-----

--Apple-Mail=_6F95CD35-22A5-4E07-9FD0-89ABF4FF74A8--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DE6BC456-3949-4DEF-A8AC-3996680FA0EA>