[PPC-VLE] Fix(ppc/il): Treat r0 as a register in e_addi/e_add16i IL #7517
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.
Description
This PR updates the Intermediate Language (IL) generation for the e_addi and e_add16i instructions on the PowerPC VLE architecture to ensure correct data-flow analysis.
Motivation and Context
For
e_addiande_add16iinstructions, the IL was incorrectly interpreting ther0register as a constant0instead of a register source. This was caused by theOTI_GPR0_ZEROflag.Changes Made
The
OTI_GPR0_ZEROflag has been removed.As a result,
r0is now correctly treated as a general-purpose register in the IL, enabling accurate data-flow analysis.operToIL(il, oper1, OTI_GPR0_ZERO, ...)operToIL(il, oper1)This ensures that r0 is consistently treated as a register operand in the IL for these instruction.
Visual Comparison