On Thu, May 16, 2024 at 12:14:09PM +0200, Aldy Hernandez wrote:
> Wait, what's the preferred way of reverting a patch? I followed what I saw
> in:
Reverting a patch (that isn't a reversion) just push git revert.
The important part is not to modify the This reverts commit line from what
git
On Thu, 2024-05-16 at 12:14 +0200, Aldy Hernandez wrote:
> Wait, what's the preferred way of reverting a patch? I followed what
> I saw in:
>
> commit 04ee1f788ceaa4c7f777ff3b9441ae076191439c
> Author: Jeff Law
> Date: Mon May 13 21:42:38 2024 -0600
>
> Revert "[PATCH v2 1/3] RISC-V:
Wait, what's the preferred way of reverting a patch? I followed what I saw in:
commit 04ee1f788ceaa4c7f777ff3b9441ae076191439c
Author: Jeff Law
Date: Mon May 13 21:42:38 2024 -0600
Revert "[PATCH v2 1/3] RISC-V: movmem for RISCV with V extension"
This reverts commit
On Thu, May 16, 2024 at 12:01:01PM +0200, Aldy Hernandez wrote:
> This reverts commit d7bb8eaade3cd3aa70715c8567b4d7b08098e699 and enables
> prange
> support again.
Please don't do this.
This breaks ChangeLog generation, will need to handle it tomorrow by hand again.
Both the ammendments to the
This reverts commit d7bb8eaade3cd3aa70715c8567b4d7b08098e699 and enables prange
support again.
---
gcc/gimple-range-cache.cc | 4 ++--
gcc/gimple-range-fold.cc | 4 ++--
gcc/gimple-range-fold.h | 2 +-
gcc/gimple-range-infer.cc | 2 +-
gcc/gimple-range-op.cc| 2 +-
