public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115673] New: [15 regression] gcc.target/i386/force-indirect-call-2.c test failure Date: Thu, 27 Jun 2024 04:48:21 +0000 [thread overview] Message-ID: <bug-115673-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115673 Bug ID: 115673 Summary: [15 regression] gcc.target/i386/force-indirect-call-2.c test failure Product: gcc Version: unknown Status: UNCONFIRMED Keywords: testsuite-fail Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org CC: rguenth at gcc dot gnu.org Target Milestone: --- I had these differences when upgrading earlier (with a patched gcc for PR115661): ``` --- a/x86_64-pc-linux-gnu/15/x86_64-pc-linux-gnu.xfail +++ b/x86_64-pc-linux-gnu/15/x86_64-pc-linux-gnu.xfail @@ -438,6 +438,7 @@ FAIL: gcc.dg/nested-vla-1.c (test for excess errors) FAIL: gcc.dg/nested-vla-2.c (test for excess errors) FAIL: gcc.dg/nested-vla-3.c (test for excess errors) FAIL: gcc.dg/packed-vla.c (test for excess errors) +FAIL: gcc.dg/pr10474.c scan-rtl-dump pro_and_epilogue "Performing shrink-wrapping" FAIL: gcc.dg/pr30473.c (test for excess errors) FAIL: gcc.dg/pr34457-1.c (test for excess errors) FAIL: gcc.dg/pr38902.c (test for excess errors) @@ -794,6 +795,7 @@ Running gcc:/gcc/testsuite/gcc.target/i386/i386.exp ... FAIL: gcc.target/i386/cet-sjlj-3.c scan-assembler-times call\t_?longjmp 1 FAIL: gcc.target/i386/cet-sjlj-5.c scan-assembler-times call\t_?longjmp 1 FAIL: gcc.target/i386/fentryname3.c scan-assembler call\t\\*nop@GOTPCREL +FAIL: gcc.target/i386/force-indirect-call-2.c scan-assembler-times (?:call|jmp)[ \\t]+\\*% 3 FAIL: gcc.target/i386/pr101716.c scan-assembler leal[\\t ][^\\n]*eax FAIL: gcc.target/i386/pr101716.c scan-assembler-not movl[\\t ][^\\n]*eax FAIL: gcc.target/i386/pr101950-2.c scan-assembler-times \txor[ql]\t 2 @@ -802,6 +804,8 @@ UNRESOLVED: gcc.target/i386/pr113689-1.c compilation failed to produce executabl FAIL: gcc.target/i386/pr85044.c (test for excess errors) FAIL: gcc.target/i386/pr86722.c scan-assembler-not orpd FAIL: gcc.target/i386/pr86722.c scan-assembler-times (?n)(?:andnpd|andpd|blendvpd) 1 +FAIL: gcc.target/i386/pr91384.c scan-assembler-not testl +FAIL: gcc.target/i386/stack-check-17.c scan-assembler-not pop === gfortran tests === ``` Picking on force-indirect-call-2.c: ``` Executing on host: /tmp/build/gcc/xgcc -B/tmp/build/gcc/ /home/sam/git/gcc/gcc/testsuite/gcc.target/i386/force-indirect-call-2.c -fdiagnostics-plain-output -O2 -mforce-indirect-call -fPIC -ffat-lto-objects -fno-ident -S -o force-indirect-call-2.s (timeout = 300) spawn -ignore SIGHUP /tmp/build/gcc/xgcc -B/tmp/build/gcc/ /home/sam/git/gcc/gcc/testsuite/gcc.target/i386/force-indirect-call-2.c -fdiagnostics-plain-output -O2 -mforce-indirect-call -fPIC -ffat-lto-objects -fno-ident -S -o force-indirect-call-2 gcc.target/i386/force-indirect-call-2.c: (?:call|jmp)[ \\t]+\\*% found 1 times FAIL: gcc.target/i386/force-indirect-call-2.c scan-assembler-times (?:call|jmp)[ \\t]+\\*% 3 ``` I assume r15-1662-g629257bcb81434?
next reply other threads:[~2024-06-27 4:48 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-27 4:48 sjames at gcc dot gnu.org [this message] 2024-06-27 4:50 ` [Bug target/115673] " sjames at gcc dot gnu.org 2024-06-27 4:50 ` [Bug rtl-optimization/115673] " pinskia at gcc dot gnu.org 2024-06-27 5:59 ` [Bug target/115673] " rguenth at gcc dot gnu.org 2024-06-27 6:02 ` sjames at gcc dot gnu.org 2024-06-28 15:23 ` sjames at gcc dot gnu.org 2024-06-30 9:53 ` rguenth at gcc dot gnu.org 2024-06-30 16:42 ` ubizjak at gmail dot com
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-115673-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).