Skip to content

[GlobalISel] Document minimum legality requirements for G_IMPLICIT_DEF. #117609

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Dec 10, 2024
Merged

[GlobalISel] Document minimum legality requirements for G_IMPLICIT_DEF. #117609

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f6d47a8
[GlobalISel] Document minimum legality requirements for G_IMPLICIT_DEF.
aemerson Nov 25, 2024
abea77e
Remove imprecise statement.
aemerson Nov 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions llvm/docs/GlobalISel/Legalizer.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -338,8 +338,8 @@ G_BUILD_VECTOR_TRUNC, G_CONCAT_VECTORS, G_UNMERGE_VALUES, G_PTRTOINT, and
G_INTTOPTR have already been noted above. In addition to those, the following
operations have requirements:

* At least one G_IMPLICIT_DEF must be legal. This is usually trivial as it
requires no code to be selected.
* For every type that can be produced by any instruction, G_IMPLICIT_DEF must be
legal.
* G_PHI must be legal for all types in the producer and consumer typesets. This
is usually trivial as it requires no code to be selected.
* At least one G_FRAME_INDEX must be legal
Expand Down
Loading