FIX: Fix the AUIPC case in ISA_IMAC to be compatible with gcc-V3.3.0#51
Open
lj-k wants to merge 1 commit intoXUANTIE-RV:mainfrom
Open
FIX: Fix the AUIPC case in ISA_IMAC to be compatible with gcc-V3.3.0#51lj-k wants to merge 1 commit intoXUANTIE-RV:mainfrom
lj-k wants to merge 1 commit intoXUANTIE-RV:mainfrom
Conversation
…-gcc-elf-newlib-x86_64-V3.3.0 In the newer compiler, like Xuantie-900-gcc-elf-newlib-x86_64-V3.3.0, the instruction "li" will be compiled as two compressed instructions, which leads to a wrong PC gap between the two AUIPC instructions in this case. We can simply move the "li" instruction ahead of the AUIPC instruction to solve this problem and make the test more robust against compiler optimizations.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 the newer compiler, like Xuantie-900-gcc-elf-newlib-x86_64-V3.3.0, the instruction "li" will be compiled as two compressed instructions, which leads to a wrong PC gap between the two AUIPC instructions in this case.
We can simply move the "li" instruction ahead of the AUIPC instruction to solve this problem and make the test more robust against compiler optimizations.