[AMDGPU] Fix handling of FP in cs.chain functions #132711
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In case there is an dynamic alloca / an alloca which is not in the entry block, cs.chain functions don't setup an FP, but are reported to need one. This results in a failed assertion in
SIFrameLowering::emitPrologue()(Assertion(!HasFP || FPSaved) && "Needed to save FP but didn't save it anywhere"' failed.) This commit changeshasFPImpl` so that the need for an SP in a cs.chain function does not directly imply the need for an FP anymore.This LLVM defect was identified via the AMD Fuzzing project.
(@rovka as discussed :) )