Skip to content

Conversation

@LebedevRI
Copy link
Member

This is just horrible.

There really should be a way to still output the normal textual diagnostics to console,
but additionally place SARIF into a file named after the object file being produced,
into a specified prefix directory.

@LebedevRI LebedevRI force-pushed the more-sarif branch 23 times, most recently from e873049 to f08fe57 Compare April 9, 2025 05:53
@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

} // namespace

int main(int argc_, char** argv_) {
return;

Check failure

Code scanning / clang

non-void function 'main' should return a value Error

non-void function 'main' should return a value
@LebedevRI LebedevRI force-pushed the more-sarif branch 5 times, most recently from de82fc9 to aa14a87 Compare April 9, 2025 06:47
@LebedevRI LebedevRI force-pushed the more-sarif branch 4 times, most recently from 5fe9218 to 69405df Compare April 9, 2025 06:56
@LebedevRI LebedevRI force-pushed the more-sarif branch 3 times, most recently from 8e5f160 to 4e5b6a3 Compare April 9, 2025 08:03
@LebedevRI
Copy link
Member Author

(Please consider upvoting:)
X-Ref: https://github.com/orgs/community/discussions/157136

@LebedevRI LebedevRI marked this pull request as draft May 13, 2025 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant