Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

C#: Extract expanded compiler arguments #15472

Merged
merged 6 commits into from Jan 31, 2024

Conversation

tamasvajk
Copy link
Contributor

No description provided.

@github-actions github-actions bot added the C# label Jan 30, 2024
Comment on lines +60 to +63
catch (Exception exc)
{
Context.ExtractionError($"Couldn't read compiler argument file: {arg}. {exc.Message}", null, null, exc.StackTrace);
}

Check notice

Code scanning / CodeQL

Generic catch clause Note

Generic catch clause.
@tamasvajk
Copy link
Contributor Author

Analysis time, per source in DCA looks good, at the same time there is some change in Stage timings. Are these within the acceptable range?

@tamasvajk tamasvajk marked this pull request as ready for review January 31, 2024 07:33
@tamasvajk tamasvajk requested a review from a team as a code owner January 31, 2024 07:33
hvitved
hvitved previously approved these changes Jan 31, 2024
Copy link
Contributor

@hvitved hvitved left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. A minor suggestion, feel free to apply or not.

try
{
var rspFileContent = System.IO.File.ReadAllText(arg[1..]);
var rspArgs = CommandLineParser.SplitCommandLineIntoArguments(rspFileContent, removeHashComments: true);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice that we can reuse this method.

Co-authored-by: Tom Hvitved <hvitved@github.com>
@@ -0,0 +1,5 @@
{
"sdk": {
"version": "8.0.100"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Depending on the merge order, this PR is relevant: #15475

@michaelnebel
Copy link
Contributor

Analysis time, per source in DCA looks good, at the same time there is some change in Stage timings. Are these within the acceptable range?

Since the overall performance looks good and since we didn't see an overall performance regression, I don't think the change in stage timings matter much, as the measure might be imprecise and since the stats update could have changed the execution order (and maybe stuff that is now faster isn't reported by DCA).

Copy link
Contributor

@michaelnebel michaelnebel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is excellent!
Thank you for also updating the stats!

@tamasvajk tamasvajk merged commit 73f96fb into github:main Jan 31, 2024
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants