Date: Fri, 01 Feb 2013 14:08:24 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Andriy Gapon <avg@FreeBSD.org>, toolchain@FreeBSD.org Cc: freebsd-hackers <freebsd-hackers@FreeBSD.org> Subject: Re: base gcc and _GLIBCXX_USE_C99 Message-ID: <510BBE48.4070101@FreeBSD.org> In-Reply-To: <510BBCAD.3070705@FreeBSD.org> References: <5106953E.2020907@FreeBSD.org> <510BBCAD.3070705@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013-02-01 14:01, Andriy Gapon wrote: > on 28/01/2013 17:11 Andriy Gapon said the following: >> I wonder why the following is the case for the base gcc. >> /usr/include/c++/4.2/bits/c++config.h: >> >> /* Define if C99 functions or macros from <wchar.h>, <math.h>, <complex.h>, >> <stdio.h>, and <stdlib.h> can be used or exposed. */ >> /* #undef _GLIBCXX_USE_C99 */ >> >> Because of this undef there is no e.g. std::strtoll(). >> Ditto for other things in stdlib.h. Maybe this support can't be enabled, because we don't expose all the required functions yet? Or maybe it is just something that was committed years ago, and then forgotten. If we are sure that all the C99 functions libstdc++ requires are now available and working, I see no problem in turning on _GLIBCXX_USE_C99.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?510BBE48.4070101>