https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105114

            Bug ID: 105114
           Summary: [12 regression] contrib/gcc_update hangs
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

On one of our older, power 7 BE machines this starting happening recently:

seurer@bns:~/gcc/git/gcc-test$ ./contrib/gcc_update
Updating GIT tree
remote: Enumerating objects: 208, done.
remote: Counting objects: 100% (208/208), done.
remote: Compressing objects: 100% (122/122), done.
remote: Total 153 (delta 122), reused 43 (delta 30), pack-reused 0
Receiving objects: 100% (153/153), 29.38 KiB | 0 bytes/s, done.
Resolving deltas: 100% (122/122), completed with 53 local objects.
>From git://gcc.gnu.org/git/gcc
   eb59ddf..5db9ce1  master     -> origin/master
First, rewinding head to replay your work on top of it...
Fast-forwarded master to 5db9ce171019f8915885cebd5cc5f4101bb926e6.
Adjusting file timestamps
Touching gcc/config.in...
Touching gcc/config/loongarch/loongarch-str.h...
Touching gcc/config/loongarch/loongarch-str.h...
Touching gcc/config/loongarch/loongarch-str.h...
Touching gcc/config/loongarch/loongarch-str.h...
Touching gcc/config/loongarch/loongarch-str.h...
...etc. forever...


Looking at the script it is getting caught here:

    while ${MAKE-make} -s -f Makefile.$$ all | grep Touching > /dev/null; do
      sleep 1
    done 2>&1

If I run the make command by hand I do indeed just get that Touching message:

seurer@bns:~/gcc/git/gcc-test$ make -s -f Makefile.28475 all
Touching gcc/config/loongarch/loongarch-str.h...
Touching gcc/config/loongarch/loongarch-str.h...
seurer@bns:~/gcc/git/gcc-test$ make -s -f Makefile.28475 all
Touching gcc/config/loongarch/loongarch-str.h...
Touching gcc/config/loongarch/loongarch-str.h...

This works fine on all our other machines, even other older power 7s.  Any
ideas what might be going wrong?

Reply via email to