Hi, we found several bugs in Bison 3.8.2, which is the latest version.
To assist in diagnosing and resolving these issues, we have attached the POC
files along with the gdb/asan logs.
Credit by: Wang Dawei and Zhou Geng, from Zhongguancun Laboratory.
Thanks for your time and attention to
On 11/26/23 17:18, Dennis Clarke via Bug reports for Bison, the GNU
parser generator wrote:
I don't quite know what to make of this result on plain jane x86_64 Linux :
.
.
.
GLIBCXX_3.4.31
GLIBCXX_3.4.32
e#
Seems strange to me ...
Never mind .. found the problem. I seem to have mul
I don't quite know what to make of this result on plain jane x86_64 Linux :
e# wc -l ./test-suite.log
45 ./test-suite.log
e# cat -n ./test-suite.log
1 ===
2 GNU Bison 3.8.2: ./test-suite.log
3 ===
I’ve encountered a test suite failure for bison-3.8.2:
623: GNU pic (Groff 1.18.1) Grammar: IELR(1) FAILED (existing.at:1460)
Here's the testsuite.log file:

Happy to provide any additional information.
Best,
Derek Clegg
Hi,
My code was relying on operator== generated in both position and location and
used to compile fine in Bison 3.6.3. I have recently upgraded to 3.8.2 and am
now getting errors on the use of such operators. I see in the source code of
location skeleton here that those are guarded by
`b4_perce
tor 2022-08-25 klockan 19:21 +0200 skrev Bruno Haible:
> Simon Josefsson wrote:
> > > In GNU gettext, many tests use "tr -d '\r'" since 2007 already,
> > > and no one
> > > ever has reported a problem with it.
> >
> > But does it fail fatally when it doesn't work? tests/parser.sh in
> > libtasn1
Bruno Haible writes:
> Since we are already stating in the generic INSTALL file, since 2008:
>
> On Solaris, don't put '/usr/ucb' early in your 'PATH'. This
> directory contains several dysfunctional programs; working variants of
> these programs are available in '/usr/bin'. So, if you
Bruno Haible writes:
> In this case, you'll better modify the unit test to pipe the result
> through "tr -d '\r'".
This is unrelated, but alas I've not found a more portable way to trim
CR than this since some tr do not support \r:
if echo solaris | tr -d '\r' | grep solais > /dev/null; then
I am looking for starting from requirements or specifications to
Pseudo-Code/Algorithm (structured English language). Then the syntax and
semantic (including code generation) as the final stage or phase.
> On 12 Nov 2021, at 23:41, Kaz Kylheku wrote:
>
> On 2021-10-14 06:23, Hans Åberg wrote:
>> Hi Akim,
>> Saw you have edited Flex, so I take it up here, even though not
>> strictly a Bison topic:
>> The Apple flex version has been edited to admit size_t sizes, 64-bit
>> on the platform, and pe
Hello Sir/Ma'am,This is Gaurav Singh, one of the many users of the Bison tool.
Thanks a lot for creating such a good tool, for it has opened a lot of new
doors to me.I've written this email in order to inform you about a bug located
in the documentation of this project( or more precisely an inco
On Fri, Jul 24, 2020 at 07:31:06AM +0200, Akim Demaille wrote:
> Hi Lars,
>
> > Le 23 juil. 2020 à 21:58, Lars Wendler a écrit :
> >
> > Hi Akim,
> >
> >> I think the problem is "simply" that your version of libtextstyle is
> >> too old.
> >>
> >> I'm using 0.20.5.
> >>
> >> https://alpha.gnu
On Wed, Jun 24, 2020 at 10:20:48AM +0200, Hans Åberg wrote:
>
>
> The problem is that I haven't changed my environment variable.
>
> > LC_ALL=UTF-8
> …
> > LC_ALL=fr_FR.UTF-8
>
> I pointed out that out: There is a double bug, locale dependent generation of
> the parser file, and relying on sof
Hello bison bug fixers -
I built C++ software (xmlInstanceParserGenerator) that reads XML schema
files and writes C++ classes and a YACC-Lex parser for XML data files
conforming to the schema files.
The Quality Information Framework (QIF) ANSI standard is defined using
22 (or 23) XML schema
14 matches
Mail list logo
