Revert ELG_LOP back to being its own target class for SV3 #701
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.
@djschlegel and @araichoor pointed out that it was probably a bad idea to change the meaning of the
ELG
bit, as I did in #700. So, this PR reverts back to the old meanings for the ELGs. To be clear, as of now (and forevermore for the purposes ofsv3
):ELG_LOP
means a low-priority ELG.ELG_HIP
means a high-priority ELG.ELG
means either a low-priority ELG or a high-priority ELG (ELG
isELG_LOP | ELG_HIP
).To ensure the correct prioritization behavior, the MTL code (for
sv3
) now utilizesELG_LOP
andELG_HIP
and ignoresELG
completely.I'll run replacement targeting files soon and email desi-targets indicating the location of the new files.