-
Notifications
You must be signed in to change notification settings - Fork 44
Disable function specialization #599
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
Disable function specialization #599
Conversation
It breaks mono's AOT compiled code, because the specialized functions are outside of generated EH frame code range. We can re-enable it, once we fix EH frame generation in mono.
akoeplinger
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! please open a runtime issue to track reenabling this
|
@radekdoulik @steveisok should we do this on the llvm-16.x branch too - it might be related to the plt_entry asserts on android |
Yes, I think that would be wise. The customer having issues on android has given us access to their repo. We should backport and try to see if that solves the problem. |
|
I updated the runtime bump PR, so we should have another CI round in few hours. Hopefully it will look fine and I will open PR for 16.x as well. |
|
/backport to dotnet/main-16.x |
|
ah, that would only work on runtime :-) |
It breaks mono's AOT compiled code, because the specialized functions are outside of generated EH frame code range. We can re-enable it, once we fix EH frame generation for mono.
Backport of Disable function specialization (#599)
It breaks mono's AOT compiled code, because the specialized functions are outside of generated EH frame code range. We can re-enable it, once we fix EH frame generation for mono.
It breaks mono's AOT compiled code, because the specialized functions are outside of generated EH frame code range. We can re-enable it, once we fix EH frame generation for mono.
It breaks mono's AOT compiled code, because the specialized functions are outside of generated EH frame code range. We can re-enable it, once we fix EH frame generation for mono.
It breaks mono's AOT compiled code, because the specialized functions are outside of generated EH frame code range. We can re-enable it, once we fix EH frame generation for mono.
It breaks mono's AOT compiled code, because the specialized functions are outside of generated EH frame code range.
We can re-enable it, once we fix EH frame generation for mono.