Remove the xcheri-rvc feature once evaluation is complete #681
Assignees
Comments
arichardson
added a commit
to arichardson/llvm-project
that referenced
this issue
Feb 9, 2023
Both hardware implementations and QEMU have supported these for a long time, so it makes sense for the compiler to default to emitting them if the "C" extension is enabled. This retains the flags that were used to enable the instructions but turns them into an opt-out flag instead. Once the exact impact of compressed CHERI instructions has been evaluated, these command line options and the SubtargetFeature can be removed. See CTSRD-CHERI#681
arichardson
added a commit
to arichardson/llvm-project
that referenced
this issue
Feb 10, 2023
Both hardware implementations and QEMU have supported these for a long time, so it makes sense for the compiler to default to emitting them if the "C" extension is enabled. This retains the flags that were used to enable the instructions but turns them into an opt-out flag instead. Once the exact impact of compressed CHERI instructions has been evaluated, these command line options and the SubtargetFeature can be removed. See CTSRD-CHERI#681
arichardson
added a commit
to arichardson/llvm-project
that referenced
this issue
Feb 13, 2023
Both hardware implementations and QEMU have supported these for a long time, so it makes sense for the compiler to default to emitting them if the "C" extension is enabled. This retains the flags that were used to enable the instructions but turns them into an opt-out flag instead. Once the exact impact of compressed CHERI instructions has been evaluated, these command line options and the SubtargetFeature can be removed. See CTSRD-CHERI#681
arichardson
added a commit
to arichardson/llvm-project
that referenced
this issue
Feb 17, 2023
Both hardware implementations and QEMU have supported these for a long time, so it makes sense for the compiler to default to emitting them if the "C" extension is enabled. This retains the flags that were used to enable the instructions but turns them into an opt-out flag instead. Once the exact impact of compressed CHERI instructions has been evaluated, these command line options and the SubtargetFeature can be removed. See CTSRD-CHERI#681
arichardson
added a commit
to arichardson/llvm-project
that referenced
this issue
Feb 17, 2023
Both hardware implementations and QEMU have supported these for a long time, so it makes sense for the compiler to default to emitting them if the "C" extension is enabled. This retains the flags that were used to enable the instructions but turns them into an opt-out flag instead. Once the exact impact of compressed CHERI instructions has been evaluated, these command line options and the SubtargetFeature can be removed. See CTSRD-CHERI#681
arichardson
added a commit
that referenced
this issue
Feb 17, 2023
Both hardware implementations and QEMU have supported these for a long time, so it makes sense for the compiler to default to emitting them if the "C" extension is enabled. This retains the flags that were used to enable the instructions but turns them into an opt-out flag instead. Once the exact impact of compressed CHERI instructions has been evaluated, these command line options and the SubtargetFeature can be removed. See #681
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Having the feature adds additional complexity and it should really be gated by presence of the C extension. However, the -mno-xcheri-rvc flag is currently still useful for evaluation of code size differences.
The text was updated successfully, but these errors were encountered: