public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/112729] New: gcc.target/i386/apx-interrupt-1.c etc. FAIL
Date: Mon, 27 Nov 2023 15:10:13 +0000 [thread overview]
Message-ID: <bug-112729-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112729
Bug ID: 112729
Summary: gcc.target/i386/apx-interrupt-1.c etc. FAIL
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: wwwhhhyyy333 at gmail dot com, zewei.mo at intel dot com
Target Milestone: ---
Target: i386-pc-solaris2.11, x86_64-unknown-freebsd12.4
Several of the gcc.target/i386/apx-*.c tests FAIL on different targets:
* On Darwin/x86 they are skipped because the assembler doesn't support the cfi
directives.
* On Solaris/x86 with the native assembler, part of the failures is for the
same reason: lack of cfi support. Instead of hardcoding more and more
targets,
I have a patch that introduces a new cfi effective-target keyword for the
testsuite to handle that properly instead.
* However, on Solaris/x86 with gas (which does support the cfi directives),
there are still quite a number of failures. I'm attaching the assembler
output for comparison.
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 130, -136 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 131, -128 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 132, -120 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 133, -112 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 134, -104 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 135, -96 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 136, -88 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 137, -80 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 138, -72 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 139, -64 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 140, -56 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 141, -48 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 142, -40 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 143, -32 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 144, -24 1
FAIL: gcc.target/i386/apx-interrupt-1.c scan-assembler-times
\\\\t\\\\.cfi_offset 145, -16 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times
.cfi_def_cfa_offset 16 2
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times
.cfi_def_cfa_offset 32 2
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times
.cfi_def_cfa_offset 48 2
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times
.cfi_def_cfa_offset 56 2
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times
.cfi_def_cfa_offset 8(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times .cfi_offset 12,
-40(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times .cfi_offset 13,
-32(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times .cfi_offset 14,
-24(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times .cfi_offset 15,
-16(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times .cfi_offset 6,
-48(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times .cfi_restore
6(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times pop2[\\\\t
]*[^\\n\\r]*%r12[^\\n\\r]*%rbp[^\\n\\r]*(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times pop2[\\\\t
]*[^\\n\\r]*%r14[^\\n\\r]*%r13[^\\n\\r]*(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times
popq[^\\n\\r]*%r15(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times push2[\\\\t
]*[^\\n\\r]*%r13[^\\n\\r]*%r14[^\\n\\r]*(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times push2[\\\\t
]*[^\\n\\r]*%rbp[^\\n\\r]*%r12[^\\n\\r]*(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2-1.c scan-assembler-times
pushq[^\\n\\r]*%r15(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
.cfi_def_cfa_offset 16 2
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
.cfi_def_cfa_offset 32 2
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
.cfi_def_cfa_offset 48 2
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
.cfi_def_cfa_offset 56 2
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
.cfi_def_cfa_offset 8(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
.cfi_offset 12, -40(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
.cfi_offset 13, -32(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
.cfi_offset 14, -24(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
.cfi_offset 15, -16(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
.cfi_offset 6, -48(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
.cfi_restore 6(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
pop2[\\\\t ]*[^\\n\\r]*%r12[^\\n\\r]*%rbp[^\\n\\r]*(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
pop2[\\\\t ]*[^\\n\\r]*%r14[^\\n\\r]*%r13[^\\n\\r]*(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
popq[^\\n\\r]*%r15(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
push2[\\\\t ]*[^\\n\\r]*%r13[^\\n\\r]*%r14[^\\n\\r]*(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
push2[\\\\t ]*[^\\n\\r]*%rbp[^\\n\\r]*%r12[^\\n\\r]*(?:\\n|[ \\\\t]+#) 1
FAIL: gcc.target/i386/apx-push2pop2_force_drap-1.c scan-assembler-times
pushq[^\\n\\r]*%r15(?:\\n|[ \\\\t]+#) 1
* I strongly suspect that the FreeBSD 12.4/x86_64 failures are the same,
although
that's difficult to tell from the gcc-testresults mails.
It seems something is amiss here: maybe the tests are Linux-specific in some
way. In that case, the tests should be adjusted accordingly.
next reply other threads:[~2023-11-27 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 15:10 ro at gcc dot gnu.org [this message]
2023-11-27 15:10 ` [Bug testsuite/112729] " ro at gcc dot gnu.org
2023-11-27 15:14 ` ro at gcc dot gnu.org
2023-11-28 2:47 ` wwwhhhyyy333 at gmail dot com
2023-11-28 3:33 ` wwwhhhyyy333 at gmail dot com
2023-11-28 12:06 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-11-28 12:11 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-11-28 12:27 ` ro at gcc dot gnu.org
2023-11-28 13:34 ` wwwhhhyyy333 at gmail dot com
2023-11-29 0:52 ` cvs-commit at gcc dot gnu.org
2023-11-29 13:52 ` cvs-commit at gcc dot gnu.org
2023-11-29 13:57 ` ro 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-112729-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).