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

[mono][jit] read DebuggableAttribute(DebuggingModes) ctor; move to metadata/ #49505

Merged

Conversation

lambdageek
Copy link
Member

Pull is_jit_optimizer_disabled out of mini into metadata.

Also support reading the DebuggingModes ctor


This is needed to properly support #47274 (the DOTNET_MODIFIABLE_ASSEMBLIES=debug env var for hot reload)

@ghost
Copy link

ghost commented Mar 11, 2021

Tagging subscribers to this area: @CoffeeFlux
See info in area-owners.md if you want to be subscribed.

Issue Details

Pull is_jit_optimizer_disabled out of mini into metadata.

Also support reading the DebuggingModes ctor


This is needed to properly support #47274 (the DOTNET_MODIFIABLE_ASSEMBLIES=debug env var for hot reload)

Author: lambdageek
Assignees: -
Labels:

area-AssemblyLoader-mono

Milestone: -

@lambdageek

This comment has been minimized.

Copy link
Member

@thaystg thaystg left a comment

Choose a reason for hiding this comment

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

LGTM.

src/mono/mono/metadata/assembly.c Outdated Show resolved Hide resolved
Pull is_jit_optimizer_disabled out of mini into metadata.

Also support reading the DebuggingModes ctor
@lambdageek lambdageek force-pushed the jit-disable-optimizations-from-enum branch from 72f660e to 0a8eed8 Compare March 11, 2021 21:07
Co-authored-by: Thays Grazia <thaystg@gmail.com>
@lambdageek
Copy link
Member Author

lambdageek commented Mar 12, 2021

@vargaz can you remember the details of 1d0195c (I can't see Xamarin bug 604486)

It doesn't look like mcs, Roslyn or F# ever emitted the DebuggableAttribute(boolean,boolean) constructor custom attribute. Always the DebuggerModes one.

I'm wondering if enabling this in mono's JIT is a good idea now. Or if we should continue ignoring it as apparently it hasn't done any harm in the last 7-10 years.

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