aboutsummaryrefslogtreecommitdiff
path: root/gcc/cp/module.cc
diff options
context:
space:
mode:
authorPalmer Dabbelt <palmer@rivosinc.com>2023-12-12 19:54:05 -0800
committerPatrick O'Neill <patrick@rivosinc.com>2024-01-24 16:37:15 -0800
commit0d1b0f2ad391217a43e9239ca017958f89e8f076 (patch)
tree990f20294492788da7733cf84130bf067e4f28b9 /gcc/cp/module.cc
parent2a9637b229f64775d82fb5917f83f71e8ad1911d (diff)
downloadgcc-0d1b0f2ad391217a43e9239ca017958f89e8f076.zip
gcc-0d1b0f2ad391217a43e9239ca017958f89e8f076.tar.gz
gcc-0d1b0f2ad391217a43e9239ca017958f89e8f076.tar.bz2
RISC-V: Don't make Ztso imply A
I can't actually find anything in the ISA manual that makes Ztso imply A. In theory the memory ordering is just a different thing that the set of availiable instructions (ie, Ztso without A would still imply TSO for loads and stores). It also seems like a configuration that could be sane to build: without A it's all but impossible to write any meaningful multi-core code, and TSO is really cheap for a single core. That said, I think it's kind of reasonable to provide A to users asking for Ztso. So maybe even if this was a mistake it's the right thing to do? gcc/ChangeLog: * common/config/riscv/riscv-common.cc (riscv_implied_info): Remove {"ztso", "a"}.
Diffstat (limited to 'gcc/cp/module.cc')
0 files changed, 0 insertions, 0 deletions