https://sourceware.org/bugzilla/show_bug.cgi?id=32527
--- Comment #2 from Phi <phi.debian at gmail dot com> --- Actually flex is not at fault, I overlooked the skeleton, each yyalloc() (i.e malloc() ) are protected by a if(!b)YY_FATAL_ERROR()... The bug is more in GCC -O3 inhability to track that b is never NULL when calling yy_init_buffer(b,...), note that yy_init_buffer() is static and then inlined in local callers when b is guaranted never NULL. Clang don't have that. Sorry for the false claim on flex. The problem on GCC is already open on GCC 13, still going on 14, so probably will take a long time to fix. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109856 I think adding one more -Wno-... in the i386_lex_CFLAGS in libcp/Makefile.am is a good way to expedite this false positive warnings fix. I thing i386_lex_CFLAGS was put in place just for this kind of hack, and this just suppress warning in the lexer, it doesn't jeopardize anything in elfutils. Cheers, Phi -- You are receiving this mail because: You are on the CC list for the bug.
