https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80369
--- Comment #2 from Adam TrhoĊ <adam.trhon at gmail dot com> ---
Could you please provide a further explanation? Why the warning in my example
should not be shown?
My background: We are setting up icecream (but it could be any other tool as
ccache or distcc) with OpenEmbedded. The build fails on ltrace, but only when
icecream is active (as it splits preprocessing and compilation). The ltrace
project has -Wall -Werror in the command and
assert(val != val);
in the code to abort in some case. Of course this should be fixed in the code,
but the gcc behavior seems confusing here.
I will also submit this to icecream (as, without further investigaion, it looks
like a problem on their side), but first I would like a comment from comunity
around gcc.
