We do not have any special handling for constant FP deopt arguments.
They are just spilled to stack or generated in register by MOVS
instruction. This is inefficient and, when we have too many such
constant arguments, may result in register allocation failure.
Instead, we can bitcast such constant Fp operands to appropriately
sized integer and record as constant into statepoint and later, into
StackMap.
Details
Details
- Reviewers
reames skatkov - Commits
- rGdedcefe09d18: [Statepoint] Constant fold FP deopt args.
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/CodeGen/SelectionDAG/StatepointLowering.cpp | ||
---|---|---|
390–391 | I guess this comment is for both constant sections. |
I guess this comment is for both constant sections.
does it make sense to move up?