https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78989

--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
...or to use a rich location to send two locations for the warning, giving:

return (asan_poison_variables &&  
                              ^~
# 6 "gimplify.cpp" 3 4
                              __null
                              ~~~~~~
                                  );

and for the logic that uses diagnostic_report_warnings_p to check all locations
in the rich location, requiring all to be within a system header for the
warning to be rejected.

Reply via email to