Hi Akim,
thank you for having a look and extracting the relevant code. GCC 11 is
wrong (together with myself); I am going to open a GCC 11 bug tonight.
Let us hope they will fix is before their release in April or March,
then Paul don't need to figure out how to work around this in Bison.
2.
Hi Akim,
thanks for sharing your thoughts! Being in charge is kind of a stretch
for an open source project like CMake. You can write a patch, open an
issue yourself, or I can try to take your advice and create a merge request.
https://gitlab.kitware.com/cmake
Bye
Christoph
Am 19.01.21 um 06:
Adrian,
See below for my stab at this issue. Unfortunately it seems to hit
a problem in GCC10, as the CI features several failures as follows:
> In file included from ../examples/c++/calc++/driver.hh:24,
> from ../examples/c++/calc++/driver.cc:20:
> ./examples/c++/calc++/parser.
Christoph,
FWIW, it appears that Bison is vastly underused in this grammar.
For instance, all these occurrences of $ should just read
$$ or $1. Who is in charge of maintaining the parsers in there?
Start:
GoalWithOptionalBackSlash {
$$ = 0;
yyGetParser->SetResult($1);
}
GoalWithOpti
[Paul, at the bottom of this message we have a warning from GCC11
that I guess you already had to keep quiet.]
Hi Christoph,
> Le 18 janv. 2021 à 22:01, Christoph Grüninger a écrit :
>
> Dear Bison community,
> while compiling CMake using GCC 11 (not yet released), I came across several
> -Wf
Dear Bison community,
while compiling CMake using GCC 11 (not yet released), I came across
several -Wfree-nonheap-object warnings. They came from a file generated
by GNU Bison 3.4.2. [1]
I was hoping the error might be fixed in a newer version, so
1. I downloaded your latest release 3.7.4
2. R
