-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
APICompat exceptions when building on MacOS arm64 #56598
Comments
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsOn an M1, execute
Apicompat will throw this:
And then right below:
|
I believe this is a known issue, a limitation of CCI, but not sure. I couldn't find the issue I remembered seeing this discussed. @ericstj do you recall? @steveisok to unblock yourself you can build with |
@safern is the plan still to switch away from ApiCompat in arcade to the new one under dotnet/sdk? If yes, what are the remaining missing features to do so? |
Yes that is the plan, however I think that'll come post 6.0 work.
We still have a few rules missing in order to be able to do that, and also the MSBuild task to run API Compat within MSBuild context, but that one should be done soon. |
Great to hear 👍 Do we have a tracking issue that I can follow along for switching over to the new ApiCompat? |
I think this is good issue listing the tasks we need to achieve to replace the old API Compat: dotnet/sdk#18678 |
Could this be related to #51250? Seems that M1 has sporadic NREs or other memory access violations. |
From what I tried, it's a consistent error, so i'm not sure the issue is related. |
This is different from the previous ARM-related CCI bug caused by alignment. This code is just running LINQ over normal reflection as part of MEF2 composition. If there is a bug here it's most likely one in the product itself (whatever version we are running tools on during the build). Line 34 in 5a55a0a
|
@steveisok does this repro with a specific version of the SDK? Could you capture a dump or more info on what version of the product it is happening? |
@steveisok in addition to @safern's question, should we keep this in 6.0 or move the 7.0? |
@safern it was off of main, so it was likely either p5 or p6. I tried main fairly recently and I don't think this is an issue an longer. |
On an M1, execute
./build.sh -Subset mono+libs -os iOSSimulator -arch arm64
Apicompat will throw this:
And then right below:
The text was updated successfully, but these errors were encountered: