-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[NativeAot] win-x86: Funclets getting double called #99687
Comments
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas |
FWIW, I expect that there is going to be a long tail of issues related to Win x86 exception handling because of #99191 (comment) . I think we may need to get both CoreCLR and NAOT onto same plan to make Win x86 support in NAOT productized (or rethink the test strategy for Win x86 NAOT). |
Very likely. I was hoping that there was some exposure of the code during linux-x86 CoreCLR bring up but apparently there are still gaps (possibly specific to the NativeAOT integration of the code).
I'm focusing on getting the runtime tests passing in this configuration which is attacking the "test strategy" angle. I am open to exploring the CoreCLR+funclets option too. I just expect to run into the same issues regardless of whether we hit them first in CoreCLR or NativeAOT, so it makes sense to investigate them. |
FWIW, linux-x86 on CoreCLR has not been brought up to our regular quality bar, and it is completely broken at the moment - #96150 (comment) .
Once you deal with the easy to repro functional issues, there are going to be stress related issues after that (GC reporting, etc.). We do not have the infrastructure like GC stress to find them on native AOT proactively. We depend on regular CoreCLR for that. |
(I'd definitely prefer not to revive the GC stress code in NativeAOT.) |
So far I tracked it down to the "tryEnd"/"tryLength" offset of |
win-x86: jitdump.x86.txt X86:
X64:
The end offset of |
I suspect this may be some artefact of |
Confirmed my suspicion. This fixes it:
|
Several of the runtime tests fail with a similar symptom:
Logs of all failed tests that hit this symptom:
testlogs.zip
The text was updated successfully, but these errors were encountered: