bug-bison
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bison 3.5.1 released


From: Hans Åberg
Subject: Re: Bison 3.5.1 released
Date: Mon, 20 Jan 2020 10:44:13 +0100

> On 20 Jan 2020, at 06:05, Akim Demaille <address@hidden> wrote:
> 
>> Le 19 janv. 2020 à 21:52, Hans Åberg <address@hidden> a écrit :
>> 
>>> On 19 Jan 2020, at 21:34, Akim Demaille <address@hidden> wrote:
>>> 
>>>> Le 19 janv. 2020 à 18:48, Hans Åberg <address@hidden> a écrit :
>>>> 
>>>>> On 19 Jan 2020, at 14:53, Akim Demaille <address@hidden> wrote:
>>>>> 
>>>>> Bison 3.5.1 fixes a few minor issues from Bison 3.5.
>>>> 
>>>> I got some make check errors, MacOS 10.15.2, same for (MacPorts) gcc9 
>>>> 9.2.0, clang 9.0.1, and Apple clang version 11.0.0:
>>>> 
>>>> 483: State number type: 128 states                   FAILED 
>>>> (torture.at:270)
>>>> 484: State number type: 129 states                   FAILED 
>>>> (torture.at:271)
>>>> 485: State number type: 256 states                   FAILED 
>>>> (torture.at:272)
>>>> 486: State number type: 257 states                   FAILED 
>>>> (torture.at:273)
>>>> 487: State number type: 32768 states                 FAILED 
>>>> (torture.at:274)
>>>> 488: State number type: 65536 states                 FAILED 
>>>> (torture.at:275)
>>>> 489: State number type: 65537 states                 FAILED 
>>>> (torture.at:276)
>>> 
>>> Thanks for the report.
>>> 
>>> Could you please send the testsuite.log file?  It should probably be
>>> zipped, it's long.
>> 
>> Which compiler?
> 
> I guess the problem is the same in all cases, so any for a start.

I use the Apple clang, as people are most likely to use that one. Which log 
files do you want?

>> —I expected you having access to the platform, or maybe it is MacOS 10.15 
>> specific, so I removed it and would need to compile it again.
> 
> No, I don't see see any failure on 10.14.6 (I don't want to experience the 
> mail migration failure you pointed me to).

There have been a number of updates, and that was only case I saw. There were 
some propblems wit MacPorts at first, but that seems to have stabilized.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]