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

Enable more ILLink tests in NativeAOT #85651

Merged
merged 16 commits into from
May 4, 2023

Conversation

vitek-karas
Copy link
Member

Product fixes:

  • Fix tracking of arrays in NativeAOT
  • Fix handling of arrays in ILLink

Test fixes:

  • Consider reflection enabled methods as marked (even if they don't have an entrypoint, like interface methods)
  • Fix where to look for ilasm
  • Better handling of compiled dependenceis
  • Ignore some more compiler generated code (which can't be marked as kept)

Enables several more data flow tests from linker for AOT as well.
Updates some bug links to point to runtime repo.

@ghost
Copy link

ghost commented May 2, 2023

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

Product fixes:

  • Fix tracking of arrays in NativeAOT
  • Fix handling of arrays in ILLink

Test fixes:

  • Consider reflection enabled methods as marked (even if they don't have an entrypoint, like interface methods)
  • Fix where to look for ilasm
  • Better handling of compiled dependenceis
  • Ignore some more compiler generated code (which can't be marked as kept)

Enables several more data flow tests from linker for AOT as well.
Updates some bug links to point to runtime repo.

Author: vitek-karas
Assignees: vitek-karas
Labels:

area-NativeAOT-coreclr

Milestone: -

@vitek-karas
Copy link
Member Author

This is ready for review - all CI failures are unrelated.

@@ -64,6 +64,20 @@ public ILScanResults Trim (ILCompilerOptions options, ILogWriter logWriter)

compilationRoots.Add (new MainMethodRootProvider (entrypointModule, CreateInitializerList (typeSystemContext, options), generateLibraryAndModuleInitializers: true));

foreach (var rootedAssembly in options.AdditionalRootAssemblies) {
// For compatibility with IL Linker, the parameter could be a file name or an assembly name.
// This is the logic IL Linker uses to decide how to interpret the string. Really.
Copy link
Member

Choose a reason for hiding this comment

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

😢 Do our tests actually use the file path case? Wondering if we can just leave it out here.

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point - I'll remove that (I just blindly copied this from ilc)

"<Module>.MainMethodWrapper()"
"<Module>.MainMethodWrapper()",

// Ignore compiler generated code which can't be reasonably matches to the source method
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
// Ignore compiler generated code which can't be reasonably matches to the source method
// Ignore compiler generated code which can't be reasonably matched to the source method

@vitek-karas vitek-karas merged commit 3232ad3 into dotnet:main May 4, 2023
@vitek-karas vitek-karas deleted the SimplerMoreILLinkTests branch May 4, 2023 07:59
@ghost ghost locked as resolved and limited conversation to collaborators Jun 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants