From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) by sourceware.org (Postfix) with ESMTPS id B2E2C3856DF8 for ; Wed, 1 Jun 2022 17:48:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B2E2C3856DF8 X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-oetec-MailScanner-From: dclarke@blastwave.org X-oetec-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.109, required 6, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, DKIM_VALID_EF -0.10, T_SCC_BODY_TEXT_LINE -0.01, URIBL_BLOCKED 0.00) X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-ID: 251Hm6RB002544 X-oetec-MailScanner-Information: Please contact oetec for more information Received: from [172.16.35.2] (cpeac202e7325b3-cmac202e7325b0.cpe.net.cable.rogers.com [99.253.170.241]) (authenticated bits=0) by mail.oetec.com (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPSA id 251Hm6RB002544 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Wed, 1 Jun 2022 13:48:07 -0400 Message-ID: Date: Wed, 1 Jun 2022 13:48:05 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 To: gcc-help Content-Language: en-US From: Dennis Clarke Subject: make check fails in the "libatomic tests" Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2022 17:48:48 -0000 Wish I knew why things fail but seem to not fail at the same time. Perhaps there is not supposed to be an error status returned back to the shell? I don't know. Anyways on an old Red Hat Enterprise Linux 6 machine ( AMD64 ) I have carefully bootstrapped GCC 12.1.0 over and over and over again. With new binutils installed also. I also built dejagnu and tcl and the usual little bits we need to run the testsuite. I should point out that this is an old slow machine ( by modern standards ) but it runs just fine. After about a day and 13 hours and 45 minutes of "make -k check" running I see this : . > > === libitm tests === Schedule of variations: unix Running target unix Using /opt/bw/share/dejagnu/baseboards/unix.exp as board description file for target. Using /opt/bw/share/dejagnu/config/unix.exp as generic interface file for target. Using ../../../../gcc-12.1.0/libitm/testsuite/config/default.exp as tool-and-target-specific interface file. Running ../../../../gcc-12.1.0/libitm/testsuite/libitm.c/c.exp ... Running ../../../../gcc-12.1.0/libitm/testsuite/libitm.c++/c++.exp ... === libitm Summary === # of expected passes 44 # of expected failures 3 # of unsupported tests 1 make[4]: Leaving directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libitm/testsuite' make[3]: Leaving directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libitm/testsuite' make[3]: Entering directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libitm' true DO=all multi-do # make make[3]: Leaving directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libitm' make[2]: Leaving directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libitm' make[2]: Entering directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libatomic' Makefile:875: warning: overriding commands for target `all-multi' Makefile:866: warning: ignoring old commands for target `all-multi' Making check in testsuite make[3]: Entering directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libatomic/testsuite' make check-DEJAGNU make[4]: Entering directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libatomic/testsuite' Making a new site.exp file ... srcdir='../../../../gcc-12.1.0/libatomic/testsuite'; export srcdir; \ EXPECT=expect; export EXPECT; \ if /bin/sh -c "runtest --version" > /dev/null 2>&1; then \ exit_status=0; l='libatomic'; for tool in $l; do \ if runtest --tool $tool --srcdir $srcdir ; \ then :; else exit_status=1; fi; \ done; \ else echo "WARNING: could not find 'runtest'" 1>&2; :;\ fi; \ exit $exit_status WARNING: Couldn't find the global config file. Using ../../../../gcc-12.1.0/libatomic/testsuite/lib/libatomic.exp as tool init file. Test run by dclarke on Wed Jun 1 07:41:54 2022 Native configuration is x86_64-pc-linux-gnu === libatomic tests === Schedule of variations: unix Running target unix Using /opt/bw/share/dejagnu/baseboards/unix.exp as board description file for target. Using /opt/bw/share/dejagnu/config/unix.exp as generic interface file for target. Using ../../../../gcc-12.1.0/libatomic/testsuite/config/default.exp as tool-and-target-specific interface file. Running ../../../../gcc-12.1.0/libatomic/testsuite/libatomic.c/c.exp ... === libatomic Summary === # of expected passes 54 make[4]: Leaving directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libatomic/testsuite' make[3]: Leaving directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libatomic/testsuite' make[3]: Entering directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libatomic' Makefile:875: warning: overriding commands for target `all-multi' Makefile:866: warning: ignoring old commands for target `all-multi' true DO=all multi-do # make make[3]: Leaving directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libatomic' make[2]: Leaving directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007/x86_64-pc-linux-gnu/libatomic' make[1]: Leaving directory `/opt/bw/build/gcc-12.1.0_rhel6_amd64.007' make: *** [do-check] Error 2 make: Target `check' not remade because of errors. real 135930.17 user 122350.27 sys 14525.06 mimas$ echo $? 0 mimas$ I have no idea what happened there and no idea how much longer things could have been left quietly churning away but there seems to be an issue in the libatomic section of life. Somewhere. Is there a way to manually isolate just this test section and then figure out what went wrong? -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional