Re: SIAL and bison 2.5

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

 




----- Original Message -----
> 
> 
> 
> Dave - here is a patch for these warnings and some others I was
> seeing with gcc 4.4.3.
> 
> -Luc

Thanks Luc -- queued for crash-6.0.3.

Dave
 
> 
> -----Original Message-----
> From: Dave Anderson [ mailto:anderson@xxxxxxxxxx ]
> Sent: Thu 1/19/2012 3:07 PM
> To: Discussion list for crash utility usage, maintenance and
> development
> Cc: Luc Chouinard
> Subject: SIAL and bison 2.5
> 
> 
> Hi Luc,
> 
> I note a new set of bison complaints on a Fedora 16 machine:
> 
> # make extensions
> gcc -Wall -nostartfiles -shared -rdynamic -o echo.so echo.c -fPIC
> -DX86_64 -DGDB_7_3_1
> gcc -Wall -nostartfiles -shared -rdynamic -o trace.so trace.c -fPIC
> -DX86_64 -DGDB_7_3_1
> gcc -Wall -nostartfiles -shared -rdynamic -o dminfo.so dminfo.c -fPIC
> -DX86_64 -DGDB_7_3_1
> cd libsial && make
> bison -psial -v -t -d sial.y
> sial.y:107.22: warning: a `;' might be needed at the end of action
> code
> sial.y:107.22: warning: future versions of Bison will not add the `;'
> sial.y:107.36: warning: a `;' might be needed at the end of action
> code
> sial.y:107.36: warning: future versions of Bison will not add the `;'
> sial.y:111.26: warning: a `;' might be needed at the end of action
> code
> sial.y:111.26: warning: future versions of Bison will not add the `;'
> sial.y:111.40: warning: a `;' might be needed at the end of action
> code
> sial.y:111.40: warning: future versions of Bison will not add the `;'
> sial.y:424.25: warning: a `;' might be needed at the end of action
> code
> sial.y:424.25: warning: future versions of Bison will not add the `;'
> sial.y:424.39: warning: a `;' might be needed at the end of action
> code
> sial.y:424.39: warning: future versions of Bison will not add the `;'
> sial.y: conflicts: 252 shift/reduce, 20 reduce/reduce
> cc -O3 -g -fPIC -c -o sial_util.o sial_util.c
> cc -O3 -g -fPIC -c -o sial_node.o sial_node.c
> cc -O3 -g -fPIC -c -o sial_var.o sial_var.c
> cc -O3 -g -fPIC -c -o sial_func.o sial_func.c
> cc -O3 -g -fPIC -c -o sial_str.o sial_str.c
> cc -O3 -g -fPIC -c -o sial_op.o sial_op.c
> cc -O3 -g -fPIC -c -o sial_num.o sial_num.c
> cc -O3 -g -fPIC -c -o sial_stat.o sial_stat.c
> cc -O3 -g -fPIC -c -o sial_builtin.o sial_builtin.c
> cc -O3 -g -fPIC -c -o sial_type.o sial_type.c
> cc -O3 -g -fPIC -c -o sial_case.o sial_case.c
> cc -O3 -g -fPIC -c -o sial_api.o sial_api.c
> cc -O3 -g -fPIC -c -o sial_member.o sial_member.c
> cc -O3 -g -fPIC -c -o sial_alloc.o sial_alloc.c
> cc -O3 -g -fPIC -c -o sial_define.o sial_define.c
> cc -O3 -g -fPIC -c -o sial_input.o sial_input.c
> cc -O3 -g -fPIC -c -o sial_print.o sial_print.c
> bison -psialpp -v -t -d sialpp.y
> sialpp.y: conflicts: 23 shift/reduce
> cc -O3 -g -fPIC -c sialpp.tab.c
> cc -O3 -g -fPIC -c sial.tab.c
> flex -L -Psial -t sial.l > lex.sial.c
> cc -O3 -g -fPIC -c lex.sial.c
> flex -Psialpp -t sialpp.l > lex.sialpp.c
> cc -O3 -g -fPIC -c lex.sialpp.c
> cc -O3 -g -fPIC -o mkbaseop mkbaseop.c
> ./mkbaseop > baseops.c
> cc -O3 -g -fPIC -c baseops.c
> ar ccurl libsial.a sial_util.o sial_node.o sial_var.o sial_func.o
> sial_str.o sial_op.o sial_num.o sial_stat.o sial_builtin.o
> sial_type.o sial_case.o sial_api.o sial_member.o sial_alloc.o
> sial_define.o sial_input.o sial_print.o sialpp.tab.o sial.tab.o
> lex.sial.o lex.sialpp.o baseops.o
> gcc -g -I.. -Ilibsial -I../gdb-7.3.1/bfd -I../gdb-7.3.1/include
> -I../gdb-7.3.1/gdb -I../gdb-7.3.1/gdb/config
> -I../gdb-7.3.1/gdb/common -I../gdb-7.3.1 -nostartfiles -shared
> -rdynamic -o sial.so sial.c -fPIC -DX86_64 -DGDB_7_3_1 -Llibsial
> -lsial
> gcc -Wall -I. -nostartfiles -shared -rdynamic -o snap.so snap.c -fPIC
> -DX86_64 -DGDB_7_3_1
> #
> 
> Since the warnings don't show up with bison 2.4.1,
> I'm guessing it's something new in version 2.5:
> 
> # bison --version
> bison (GNU Bison) 2.5
> Written by Robert Corbett and Richard Stallman.
> 
> Copyright (C) 2011 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There
> is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> #
> 
> Probably worth cleaning up now rather than later?
> 
> Thanks,
> Dave
> 
> 

--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility


[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux