https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613
--- Comment #23 from David Malcolm <dmalcolm at gcc dot gnu.org> --- (In reply to David Malcolm from comment #21) [...snip...] > > FWIW SARIF has a distinction between a "result" and a "notification" where > the former refer to the software under test, and the latter to the testing > (e.g. a "tool configuration notification" could be "I can't read the config > file to start this run"). Currently GCC doesn't make such a distinction; > perhaps it should. Specifically, SARIF tool components can have notifications, and SARIF invocation objects can have: * 3.20.21 toolExecutionNotifications property * 3.20.22 toolConfigurationNotifications property See e.g. "K.4 Comprehensive SARIF file" https://docs.oasis-open.org/sarif/sarif/v2.1.0/errata01/os/sarif-v2.1.0-errata01-os-complete.html#_Toc141791202 which has an examples of: * various results about the software-under-test found by the tool * a "toolConfigurationNotifications" entry for a problem seen in the tool's config file * various "toolExecutionNotifications" entries, including one for an exception when running the tool (leading to the run being incomplete) Currently GCC handles internal compiler errors as toolExecutionNotifications, and everything else as results.
