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 testsuite/100346] New: [11 regression] printf tests fail after r11-6755 Date: Thu, 29 Apr 2021 22:54:42 +0000 [thread overview] Message-ID: <bug-100346-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100346 Bug ID: 100346 Summary: [11 regression] printf tests fail after r11-6755 Product: gcc Version: 11.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:3804e937b0e252a7e42632fe6d9f898f1851a49c, r11-6755 There are 3 similar failures starting with this revision on a powerpc64 power 9 LE system. I tried this on some other systems (power 7, 8, and 10) and on all of them the tests were flagged as unsupported so perhaps that is all that is needed here? commit 3804e937b0e252a7e42632fe6d9f898f1851a49c (HEAD) Author: Mark Wielaard <mark@klomp.org> Date: Tue Sep 29 15:52:44 2020 +0200 Default to DWARF5 make -k check-gcc RUNTESTFLAGS="execute.exp=gcc.c-torture/execute/user-printf.c" FAIL: gcc.c-torture/execute/user-printf.c -O3 -g (test for excess errors) # of expected passes 15 # of unexpected failures 1 spawn -ignore SIGHUP /home3/seurer/gcc/git/build/gcc-11-test/gcc/xgcc -B/home3/seurer/gcc/git/build/gcc-11-test/gcc/ /home/seurer/gcc/git/gcc-11-test/gcc/testsuite/gcc.c-torture/execute/user-printf.c -fdiagnostics-plain-output -O3 -g -w -lm -o ./user-printf.exe /usr/bin/ld: Dwarf Error: Can't find .debug_ranges section. /tmp/ccqaXtoD.o: In function `main': user-printf.c:(.text.startup+0x20): warning: the use of `tmpnam' is dangerous, better use `mkstemp' FAIL: gcc.c-torture/execute/user-printf.c -O3 -g (test for excess errors) make -k check-gcc RUNTESTFLAGS="execute.exp=gcc.c-torture/execute/printf-2.c" FAIL: gcc.c-torture/execute/printf-2.c -O3 -g (test for excess errors) # of expected passes 13 # of unexpected failures 1 spawn -ignore SIGHUP /home3/seurer/gcc/git/build/gcc-11-test/gcc/xgcc -B/home3/seurer/gcc/git/build/gcc-11-test/gcc/ /home/seurer/gcc/git/gcc-11-test/gcc/testsuite/gcc.c-torture/execute/printf-2.c -fdiagnostics-plain-output -O3 -g -w -lm -o ./printf-2.exe /usr/bin/ld: Dwarf Error: Can't find .debug_ranges section. /tmp/ccDgL46Y.o: In function `main': printf-2.c:(.text.startup+0x20): warning: the use of `tmpnam' is dangerous, better use `mkstemp' FAIL: gcc.c-torture/execute/printf-2.c -O3 -g (test for excess errors) Excess errors: /usr/bin/ld: Dwarf Error: Can't find .debug_ranges section. make -k check-gcc RUNTESTFLAGS="execute.exp=gcc.c-torture/execute/fprintf-2.c" FAIL: gcc.c-torture/execute/fprintf-2.c -O3 -g (test for excess errors) # of expected passes 13 # of unexpected failures 1 spawn -ignore SIGHUP /home3/seurer/gcc/git/build/gcc-11-test/gcc/xgcc -B/home3/seurer/gcc/git/build/gcc-11-test/gcc/ /home/seurer/gcc/git/gcc-11-test/gcc/testsuite/gcc.c-torture/execute/fprintf-2.c -fdiagnostics-plain-output -O3 -g -w -lm -o ./fprintf-2.exe /usr/bin/ld: Dwarf Error: Can't find .debug_ranges section. /tmp/ccki8IKn.o: In function `main': fprintf-2.c:(.text.startup+0x20): warning: the use of `tmpnam' is dangerous, better use `mkstemp' FAIL: gcc.c-torture/execute/fprintf-2.c -O3 -g (test for excess errors) Excess errors: /usr/bin/ld: Dwarf Error: Can't find .debug_ranges section.
next reply other threads:[~2021-04-29 22:54 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-29 22:54 seurer at gcc dot gnu.org [this message] 2021-04-30 6:56 ` [Bug testsuite/100346] " rguenth at gcc dot gnu.org 2021-04-30 8:40 ` jakub at gcc dot gnu.org 2021-04-30 20:33 ` seurer at gcc dot gnu.org 2021-07-28 7:06 ` [Bug testsuite/100346] [11/12 " rguenth at gcc dot gnu.org 2022-04-21 7:49 ` rguenth at gcc dot gnu.org 2023-05-29 10:04 ` [Bug testsuite/100346] [11/12/13/14 " jakub 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-100346-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: linkBe 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).