aboutsummaryrefslogtreecommitdiff
path: root/gcc/range-op-float.cc
diff options
context:
space:
mode:
authorJeff Law <jeffreyalaw@gmail.com>2023-08-03 10:57:23 -0400
committerJeff Law <jeffreyalaw@gmail.com>2023-08-03 10:57:23 -0400
commitd61efa3cd3378be38738bfb5139925d1505c1325 (patch)
tree60448767de036c3f4b31319f8ab4abdf3e856a79 /gcc/range-op-float.cc
parentf80efa49b7a1639b0d6e9bcea8cf38850d037a02 (diff)
downloadgcc-d61efa3cd3378be38738bfb5139925d1505c1325.zip
gcc-d61efa3cd3378be38738bfb5139925d1505c1325.tar.gz
gcc-d61efa3cd3378be38738bfb5139925d1505c1325.tar.bz2
[committed][RISC-V] Remove errant hunk of code
I'm using this hunk locally to more thoroughly exercise the zicond paths due to inaccuracies elsewhere in the costing model. It was never supposed to be part of the costing commit though. And as we've seen it's causing problems with the vector bits. While my testing isn't complete, this hunk was never supposed to be pushed and it's causing problems. So I'm just ripping it out. There's a bigger TODO in this space WRT a top-to-bottom evaluation of the costing on RISC-V. I'm still formulating what that evaluation is going to look like, so don't hold your breath waiting on it. Pushed to the trunk. gcc/ * config/riscv/riscv.cc (riscv_rtx_costs): Remove errant hunk from recent commit.
Diffstat (limited to 'gcc/range-op-float.cc')
0 files changed, 0 insertions, 0 deletions