Closed patrick-rivos closed 7 months ago
Cancelled it since it had 3 patches - I was only trying to test with one :-/
Using --reject shows hunks like:
> git am --reject ../../patrick/0001-RISC-V-Use-riscv_subword_address-for-atomic_test_and.patch
Applying: RISC-V: Use riscv_subword_address for atomic_test_and_set
Checking patch gcc/config/riscv/sync.md...
error: while searching for:
emit_insn (gen_atomic_fetch_orsi (old, aligned_mem, shifted_set, model));
emit_move_insn (old, gen_rtx_ASHIFTRT (SImode, old,
gen_lowpart (QImode, shift)));
emit_move_insn (operands[0], gen_lowpart (QImode, old));
DONE;
})
error: patch failed: gcc/config/riscv/sync.md:530
Checking patch gcc/config/riscv/sync.md...
Applying patch gcc/config/riscv/sync.md with 1 reject...
Rejected hunk #1.
Applied patch gcc/config/riscv/sync.md cleanly.
Patch failed at 0001 RISC-V: Use riscv_subword_address for atomic_test_and_set
hint: Use 'git am --show-current-patch=diff' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
This produced outputs like this:
Much more helpful when debugging why a patch doesn't apply IMO.