-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
DEREF_OF_NULL in /src/coreclr/jit/lsrabuild.cpp #93048
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsDescriptionPointer runtime/src/coreclr/jit/lsraxarch.cpp Lines 211 to 214 in e40b3ab
where it is dereferenced at Found by Linux Verification Center (portal.linuxtesting.ru) with SVACE. Author E. Bykhanova. Reproduction Steps. Expected behavior. Actual behavior. Regression?No response Known WorkaroundsNo response ConfigurationNo response Other informationNo response
|
Looks like dead code, we don't have those kind of passthrough GT_NOP nodes in LIR. |
Rationalization removes all GT_NOP nodes, and we do not seem to introduce any of these before LSRA (and especially not the typed "passthrough" GT_NOP nodes). This code is just wrong for the passthrough nodes, so just switch all the LSRA code to only handle potential void NOPs. Fix dotnet#93048
Rationalization removes all GT_NOP nodes, and we do not seem to introduce any of these before LSRA (and especially not the typed "passthrough" GT_NOP nodes). This code is just wrong for the passthrough nodes, so just switch all the LSRA code to only handle potential void NOPs. Fix #93048
Pointer
GenTree::gtGetOp1(...)
, that can have only NULL value, is passed as 1st parameter in call to functionLinearScan::BuildUse
runtime/src/coreclr/jit/lsraxarch.cpp
Lines 211 to 216 in e40b3ab
where it is dereferenced at
runtime/src/coreclr/jit/lsrabuild.cpp
Lines 2929 to 2930 in e40b3ab
runtime/src/coreclr/jit/lsrabuild.cpp
Lines 2964 to 2967 in e40b3ab
Found by Linux Verification Center (portal.linuxtesting.ru) with SVACE.
Author E. Bykhanova.
The text was updated successfully, but these errors were encountered: