Hi Steve,
I would do git am pr88076_v1_1.patch or patch -p1 <pr88076_v1_1.patch for
each of the patch files. Then they go where they ought to be.
Pro tip: create a new branch before doing the git am, then you can just
switch back to master when desired.
- Andre
Andre Vehreschild * ve...@gmx.de
Am 29. Juni 2025 20:29:21 schrieb Steve Kargl
<s...@troutmask.apl.washington.edu>:
On Sun, Jun 29, 2025 at 10:35:39AM -0700, Steve Kargl wrote:
Just applied the 6 patch (with the update part 5). I'm
seeing a significant increase in the number of failures
in 'make check-fortran' testing.
Just re-applied your patches in the top-level gcc/ directory.
I was expecting most changes to appear in gcc/gcc/fortran
and gcc/libgfortran. These files are dumped into gcc/
alloc.c alloc.h allocator.c allocator.h collective_subroutine.c
collective_subroutine.h counter_barrier.c counter_barrier.h
hashmap.c hashmap.h shared_memory.c shared_memory.h
supervisor.c supervisor.h sync.c sync.h teams_mgmt.c
teams_mgmt.h thread_support.c thread_support.h
Am I doing something wrong? For the record, I do
cd gcc/
patch < ../pr88076_v1_1.patch
patch < ../pr88076_v1_2.patch
patch < ../pr88076_v1_3.patch
patch < ../pr88076_v1_4.patch
patch < ../pr88076_v1_5.patch
patch < ../pr88076_v1_6.patch
--
Steve
