public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/100820] New: [12 regression] bootstrap hangs during stage2 on power 10
Date: Fri, 28 May 2021 18:44:56 +0000	[thread overview]
Message-ID: <bug-100820-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 100820
           Summary: [12 regression] bootstrap hangs during stage2 on power
                    10
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

g:a8764071f2eb6b4cdc9ecb788dfaa2b095b52598, r12-1020

Author: Aaron Sawdey <acsawdey@linux.ibm.com>
Date:   Tue Mar 2 18:06:37 2021 -0600
    Fusion patterns for add-logical/logical-add

This is causing a hang during stage2 of bootstrapping for trunk on power 10.  I
tried r12-1019 and it was fine.

Here is one example that happens when configure is running:

. . .
checking for powerpc64le-unknown-linux-gnu-gfortran...
/home/seurer/gcc/git/build/gcc-trunk-bootstrap/./gcc/gfortran
-B/home/seurer/gcc/git/build/gcc-trunk-bootstrap/./gcc/
-B/home/seurer/gcc/git/install/gcc-trunk-bootstrap/powerpc64le-unknown-linux-gnu/bin/
-B/home/seurer/gcc/git/install/gcc-trunk-bootstrap/powerpc64le-unknown-linux-gnu/lib/
-isystem
/home/seurer/gcc/git/install/gcc-trunk-bootstrap/powerpc64le-unknown-linux-gnu/include
-isystem
/home/seurer/gcc/git/install/gcc-trunk-bootstrap/powerpc64le-unknown-linux-gnu/sys-include
  -fno-checking
checking whether we are using the GNU Fortran compiler... 
(and here it hangs)


3912958 pts/0    R+     2:12
/home/seurer/gcc/git/build/gcc-trunk-bootstrap/./gcc/f951 conftest.F
-ffixed-form -cpp=/tmp/cc5vO5dZ.f90 -quiet -iprefix
/home/seurer/gcc/git/build/gcc-trunk-bootstrap/gcc/../lib/gcc/powerpc64le-unknown-linux-gnu/12.0.0/
-isystem /home/seurer/gcc/git/build/gcc-trunk-bootstrap/./gcc/include -isystem
/home/seurer/gcc/git/build/gcc-trunk-bootstrap/./gcc/include-fixed -isystem
/home/seurer/gcc/git/install/gcc-trunk-bootstrap/powerpc64le-unknown-linux-gnu/include
-isystem
/home/seurer/gcc/git/install/gcc-trunk-bootstrap/powerpc64le-unknown-linux-gnu/sys-include
conftest.F -quiet -dumpbase conftest.F -dumpbase-ext .F -mcpu=power10
-fno-checking -fintrinsic-modules-path finclude
-fpre-include=/usr/include/finclude/math-vector-fortran.h -o /tmp/cc6Kgdbr.s

This should finish almost instantly but never does.

seurer@ltcden2-lp1:~/gcc/git/build/gcc-trunk-bootstrap$ cat
./powerpc64le-unknown-linux-gnu/libgomp/conftest.F
      program main
#ifndef __GNUC__
       choke me
#endif

      end

             reply	other threads:[~2021-05-28 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 18:44 seurer at gcc dot gnu.org [this message]
2021-05-28 19:19 ` [Bug target/100820] " pinskia at gcc dot gnu.org
2021-06-04 12:57 ` seurer at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-100820-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).