Ticket #275 (closed bug: fixed)

Opened 5 years ago

Last modified 5 years ago

In maint mode, IMCC does not build with bison 2.4.x

Reported by: Infinoid Owned by: NotFound
Priority: normal Milestone:
Component: none Version:
Severity: medium Keywords:
Cc: Language:
Patch status: Platform:

Description

Generating sources from imcc.y with bison 2.3 results in:

bison -v -y compilers/imcc/imcc.y -d -o compilers/imcc/imcparser.c
compilers/imcc/imcc.y:1315.6-1344.78: warning: unused value: $3
compilers/imcc/imcc.y:1774.6-1782.10: warning: unused value: $2
compilers/imcc/imcc.y:1827.6-1833.43: warning: unused value: $2
conflicts: 1 shift/reduce

However, building with bison 2.4.1 results in:

bison -v -y compilers/imcc/imcc.y -d -o compilers/imcc/imcparser.c
compilers/imcc/imcc.y:1829.12-13: $$ for the midrule at $2 of `get_results' has no declared type
compilers/imcc/imcc.y:1830.12-13: $$ for the midrule at $2 of `get_results' has no declared type
compilers/imcc/imcc.y:1831.12-13: $$ for the midrule at $2 of `get_results' has no declared type
compilers/imcc/imcc.y:1910.12-13: $$ for the midrule at $2 of `sub_call' has no declared type
make: *** [compilers/imcc/imcparser.c] Error 1

(If it matters, both tests were done with flex 2.5.35.)

Can IMCC be adapted to work with the newer bison?

Change History

Changed 5 years ago by NotFound

Attempt to fix commited in r36384, but I can't test now with bison 2.4

Changed 5 years ago by NotFound

  • status changed from new to assigned
  • owner set to NotFound

After fixing another problem in r36385, verified that it builds with bison with 2.4.1 in talks in #parrot Waiting for some more feedback.

Changed 5 years ago by NotFound

  • status changed from assigned to closed
  • resolution set to fixed

No complaints in several days, closing ticket.

Note: See TracTickets for help on using tickets.