https://sourceware.org/bugzilla/show_bug.cgi?id=32527
Phi changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://sourceware.org/bugzilla/show_bug.cgi?id=32527
--- Comment #3 from Phi ---
Hi Sam,
Sorry I didn't saw your email, I did reply directly in the bugzilla ticket,
the problem is not flex as I first thought but more GCC -O3, I let you read
what I wrote there.
I think the propose fix is harmle
https://sourceware.org/bugzilla/show_bug.cgi?id=32527
--- Comment #2 from Phi ---
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
https://sourceware.org/bugzilla/show_bug.cgi?id=32527
--- Comment #1 from Sam James ---
(In reply to Phi from comment #0)
> Since we have little chance to get the lexer skeleton fixed from flex team,
> a possible workaround is to add the option -Wno-null-dereference in the file
> elfutils/libcpu
