From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============8287489915592487450=="
MIME-Version: 1.0
From: Petr Machata <pmachata@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH 1/2] Enable C++
Date: Tue, 07 Apr 2015 19:10:40 +0200
Message-ID: <87h9sreuen.fsf@redhat.com>
In-Reply-To: 1428420433.5539.60.camel@bordewijk.wildebeest.org

--===============8287489915592487450==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Mark Wielaard <mjw@redhat.com> writes:

> I was mostly wondering whether we needed to add an command line argument
> like -std=3Dgnu++98 to be sure. But maybe that is all implicit and
> standard for all gcc versions anyway.

Actually I can't find code that c++98 mode would reject and gnu++98
would allow.  -pedantic makes all the difference, and it makes it
regardless of the dialect chosen.

Which makes it kinda hard to actually test for gnu++98 support.  Which I
think we formally need, for all the GNU C stuff that we get in C headers
((struct X) {blah, blah}, long long literals, __VA_ARGS__).  But GCC
happily compiles that in c++98 mode anyway.

So, I don't know.  Maybe I just compile the test case with -std=3Dgnu++98
and make it "Checking for working C++ compiler that accepts -std=3Dgnu++98"?

Clang knows about the option as well, FWIW.

Thanks,
Petr

--===============8287489915592487450==--