Date: Thu, 24 Mar 2016 16:18:35 -0700 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Dimitry Andric <dim@FreeBSD.org> Cc: toolchain@FreeBSD.org Subject: Re: CXXSTD=c++11 Message-ID: <56F475CB.8020107@FreeBSD.org> In-Reply-To: <DE6BC456-3949-4DEF-A8AC-3996680FA0EA@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> <DE6BC456-3949-4DEF-A8AC-3996680FA0EA@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --72KcMDTBSS05IlpagUU89KU6E1qdEbQkC Content-Type: multipart/mixed; boundary="CdnB6dMWhHgMpuiB9gnoXRFTV8npTHra0" From: Bryan Drewery <bdrewery@FreeBSD.org> To: Dimitry Andric <dim@FreeBSD.org> Cc: toolchain@FreeBSD.org Message-ID: <56F475CB.8020107@FreeBSD.org> Subject: Re: CXXSTD=c++11 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> <DE6BC456-3949-4DEF-A8AC-3996680FA0EA@FreeBSD.org> In-Reply-To: <DE6BC456-3949-4DEF-A8AC-3996680FA0EA@FreeBSD.org> --CdnB6dMWhHgMpuiB9gnoXRFTV8npTHra0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 3/24/2016 4:16 PM, Dimitry Andric wrote: > 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=3Dc++11 (there's more discussion in that link a= nd 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 i= n >> sys/cdefs.h? We shouldn't litter contrib code with #ifdef GCC_VERSION= >> blocks. >=20 > 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=3Dc++= 11. > This was so you could even build it with gcc 4.2.1 from base. >=20 > However, it really doesn't make much sense to do so, and upstream > libcxxrt simply uses static_assert directly, and requires -std=3Dc++11.= I > will update the libcxxrt build to do so, probably tomorrow. >=20 Sounds good. --=20 Regards, Bryan Drewery --CdnB6dMWhHgMpuiB9gnoXRFTV8npTHra0-- --72KcMDTBSS05IlpagUU89KU6E1qdEbQkC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJW9HXLAAoJEDXXcbtuRpfPmsgH+gKrS1a/H5pBO8mU73b6OiPx yDu+tFCfAIUH1RiP3vNA4zMb7+VrchFn6mTs3/DdJy6j41g6W8j6hMCQTF8ylnBL pBEdJ2izX9asq0C3iHPR9a75UDnYRS5Q4dmnWByR+nR1vegA5bbH5NCqHWvkTJdn vvmJOp0zpqNQyxxLKSy/Z8JyKcBQSj8mJDTidGsbSG8e58JhzBr5yjtsapMV4Mxj aWMl8CySnkLF0vBpYGfn6QY8XxVpD5rB777+mpjOLydOn3PvKAc/69hZB71CjxZ4 FMk6jbSbebXDH+8KyaO6c2drifMkwTxiPu8j+y25jKz2e3X3AwwBlKWXmWayzhU= =t0kt -----END PGP SIGNATURE----- --72KcMDTBSS05IlpagUU89KU6E1qdEbQkC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56F475CB.8020107>