You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[ARM32] Display wrong register number for double registers #8121
It seems to be not a trivial job to make it print out double registers for ARM32 correctly, because there are different paths to get a name of ARM32 double registers.
COMPlus_JitDump
Each phase use different method to print out register name.
COMPlus_JitDisasm
For example, each phase of JIT compiler use different way to print out double registers, i.e. calling getRegNameFloat(), getRegName(), compRegVarName(), emitRegName() and etc.
In addition, I've a concern that if I changed this, then it will introduce a lot of differences in jit-diff for ARM32 codegen.
I think for arm32 legacy_backend, we just lived with it, since while it is confusing, once you understand it, there is no ambiguity. It would be nice to fix it, though.
I've a concern that if I changed this, then it will introduce a lot of differences in jit-diff for ARM32 codegen.
That is true, but would be a one-time, temporary thing.
Activity
karelz commentedon May 16, 2017
My appologies, I moved the wrong bug by accident, reopening ...
hqueue commentedon May 17, 2017
It seems to be not a trivial job to make it print out double registers for ARM32 correctly, because there are different paths to get a name of ARM32 double registers.
For example, each phase of JIT compiler use different way to print out double registers, i.e. calling
getRegNameFloat(),getRegName(),compRegVarName(),emitRegName()and etc.In addition, I've a concern that if I changed this, then it will introduce a lot of differences in jit-diff for ARM32 codegen.
Do you have any idea ?
BruceForstall commentedon May 18, 2017
I think for arm32 legacy_backend, we just lived with it, since while it is confusing, once you understand it, there is no ambiguity. It would be nice to fix it, though.
That is true, but would be a one-time, temporary thing.
hqueue commentedon May 18, 2017
Right, if we are aware of it, there is no problem.
Because there are other urgent issues in ryujit/arm32, I'm going to leave it as future task and just notify it to other arm32 contributors.
@dotnet/arm32-contrib Please be aware that double register number in JitDump and JitDisam is not correct for ARM32 in both LegacyJIT and RyuJIT.
BruceForstall commentedon Aug 2, 2017
Since this isn't required to ship RyuJIT/ARM32, I'm removing it from the RyuJIT/ARM32 project.
AndyAyersMS commentedon Feb 23, 2018
@BruceForstall seems like this should be moved to Future...?
BruceForstall commentedon Feb 23, 2018
Yes. Done.
kunalspathak commentedon Dec 23, 2022
I can confirm the problem still exists.