On Mon, Jan 09, 2017 at 09:10:06AM -0500, Nathan Sidwell wrote:
> On 01/09/2017 09:03 AM, Jakub Jelinek wrote:
>
> > FAIL: g++.dg/cpp1z/constexpr-if10.C (test for excess errors)
> >
> > Could we do e.g.
> > sed -i -e 's/long long/int */g' testsuite/g++.dg/cpp1z/constexpr-if10.C
> > so that it i
On 01/09/2017 09:03 AM, Jakub Jelinek wrote:
FAIL: g++.dg/cpp1z/constexpr-if10.C (test for excess errors)
Could we do e.g.
sed -i -e 's/long long/int */g' testsuite/g++.dg/cpp1z/constexpr-if10.C
so that it is something where if constexpr will be always true?
that would seem fine to me
nath
On Mon, Jan 09, 2017 at 08:49:25AM -0500, Nathan Sidwell wrote:
> On 01/08/2017 01:34 AM, Jason Merrill wrote:
> > P0292 defines the notion of "discarded statement" which is almost but
> > not quite the same as "unevaluated operand". This PR shows a case
> > where we need to be able to tell that w
On 09/01/17 13:49, Nathan Sidwell wrote:
On 01/08/2017 01:34 AM, Jason Merrill wrote:
P0292 defines the notion of "discarded statement" which is almost but
not quite the same as "unevaluated operand". This PR shows a case
where we need to be able to tell that we're in a discarded statement
at
On 01/08/2017 01:34 AM, Jason Merrill wrote:
P0292 defines the notion of "discarded statement" which is almost but
not quite the same as "unevaluated operand". This PR shows a case
where we need to be able to tell that we're in a discarded statement
at a lower level than in the parser, so this p
P0292 defines the notion of "discarded statement" which is almost but
not quite the same as "unevaluated operand". This PR shows a case
where we need to be able to tell that we're in a discarded statement
at a lower level than in the parser, so this patch moves the
information about being in a dis
