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++/CLI assemblies are not eligible for crossgen2 #83942

Open
szilvaa-adsk opened this issue Mar 26, 2023 · 0 comments
Open

C++/CLI assemblies are not eligible for crossgen2 #83942

szilvaa-adsk opened this issue Mar 26, 2023 · 0 comments
Labels
Milestone

Comments

@szilvaa-adsk
Copy link
Contributor

Description

Our application that uses large C++/CLI assemblies starts slower than it did on .net framework 4.8. Profiling shows a lot of JIT activity but Crossgen2 reports

Error: Error: managed C++ is not supported: <dll name>

Configuration

x64 windows.

Regression?

Yes. NGEN on .net framework used to work for C++/CLI assemblies.

Data

According to PerfView results ~20% of startup is spent in JIT.

Analysis

@szilvaa-adsk szilvaa-adsk added the tenet-performance Performance related issue label Mar 26, 2023
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Mar 26, 2023
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Mar 26, 2023
@huoyaoyuan huoyaoyuan added area-crossgen2-coreclr and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Mar 26, 2023
@mangod9 mangod9 removed the untriaged New issue has not been triaged by the area owner label Apr 3, 2023
@mangod9 mangod9 added this to the Future milestone Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants