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

Add linux-riscv64 in ILCompilerSupportedRids #45852

Merged
merged 3 commits into from
Jan 10, 2025

Conversation

am11
Copy link
Member

@am11 am11 commented Jan 10, 2025

Related to dotnet/runtime#110688.

cc @dotnet/samsung, @akoeplinger, @jkoritzinsky

@ViktorHofer
Copy link
Member

Updating with latest main as we had a build break that just got fixed with 6b3a36d

@am11
Copy link
Member Author

am11 commented Jan 10, 2025

/ba is showing a new failure in TemplateEngine, which is unrelated to the change.

@@ -387,7 +387,11 @@

<!-- The subset of ILCompiler target RIDs that are officially supported. Should be a subset of
Copy link
Member

Choose a reason for hiding this comment

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

This comment says that this list should be a subset of ILCompilerRIDs.props, but it is not the case. Does the comment or ILCompilerRIDs.props need updating?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes it's not strictly a subset. We include the official RIDs then the current OutputRID, which covers a set that is not a superset of all the allowed RIDs. I will update the comment.

@@ -387,7 +387,11 @@

<!-- The subset of ILCompiler target RIDs that are officially supported. Should be a subset of
https://github.com/dotnet/runtime/blob/main/src/installer/pkg/projects/Microsoft.DotNet.ILCompiler/ILCompilerRIDs.props -->
<ILCompilerSupportedRids Include="@(Net90ILCompilerSupportedRids)" />
<ILCompilerSupportedRids Include="
Copy link
Member

Choose a reason for hiding this comment

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

All other lists have a version number. Should this one have a version number as well?

Copy link
Member

Choose a reason for hiding this comment

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

this is fine. we need one item that represents the "current" list, this is that.

Copy link
Member

Choose a reason for hiding this comment

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

Should other community supported architectures be moved to the "current" list?

Copy link
Member Author

@am11 am11 Jan 10, 2025

Choose a reason for hiding this comment

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

Next version properties are added around preview 1 I think. Currently, net10 is using version less properties.

Should other community supported architectures be moved to the "current" list?

It is the inheritance chain. For each component, the RID is listed once under the .NET version where its support was enabled. The next version property just inherits the previous one. LoongArch was handled last year https://github.com/dotnet/installer/pull/19469/files.

Copy link
Member

Choose a reason for hiding this comment

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

I think we add the next version properties when we do branching, i.e. for net11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants