Re: [SPAM] [GNU Bison 2.3] testsuite: 155 failed

[Christian Kellermann]

Hi Joel,

* Joel E. Denny <address@hidden> [070128 21:39]:
> On Sun, 28 Jan 2007, Christian Kellermann wrote:
> 
> > I am in the progress of updating OpenBSD's GNU bison port to 2.3.
> > The compilation works without errors. During the regression tests,
> > there are failures. I have attached the testsuite.log. If there is
> > anymore information I can provide I will happily do so.
> 
> Thanks for the report.
Sorry for my late reply. Please find my results below.

> Please try the following commands from the root of your Bison build:
> What output do you get?
>   cd tests
>   ./testsuite -d 155

[Banners omitted]
155: Incorrect lookahead during nondeterministic GLRFAILED 
(glr-regression.at:1405)

>   cd testsuite.dir/155
>   ../../bison -o glr-regr14.c glr-regr14.y 

glr-regr14.y: conflicts: 3 reduce/reduce

>   cc glr-regr14.c

glr-regr14.y:38: warning: `union YYSTYPE' declared inside parameter list
glr-regr14.y:38: warning: its scope is only this definition or
declaration, which is probably not what you want
glr-regr14.y:38: warning: parameter has incomplete type
glr-regr14.y:38: warning: parameter has incomplete type
glr-regr14.c: In function `yyuserMerge':
glr-regr14.c:1050: error: type of formal parameter 1 is incomplete
glr-regr14.c:1050: error: type of formal parameter 2 is incomplete
glr-regr14.y: At top level:
glr-regr14.y:183: warning: `union YYSTYPE' declared inside parameter
list
glr-regr14.y:184: error: parameter `s1' has incomplete type
glr-regr14.y:184: error: parameter `s2' has incomplete type


> 
> Now edit the file glr-regr14.y by replacing all occurrences of:
> 
>   union YYSTYPE
> 
> with just:
> 
>   YYSTYPE
> 
> There should be four instances.  Run:

done.

>   ../../bison -o glr-regr14.c glr-regr14.y

glr-regr14.y: conflicts: 3 reduce/reduce

>   cc glr-regr14.c

none, compiles without warnings.

Does this help you further? What implications does this have for my
port? Should I include a patch removing those union declarations?

Thank you very much,

Christian

-- 
You may use my gpg key for replies:
pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

pgpVjdn7vw4ZK.pgp
Description: PGP signature