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 target/102835] New: gcc.target/i386/avx512fp16-trunchf.c FAILs
Date: Tue, 19 Oct 2021 11:41:56 +0000 [thread overview]
Message-ID: <bug-102835-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102835
Bug ID: 102835
Summary: gcc.target/i386/avx512fp16-trunchf.c FAILs
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: wwwhhhyyy333 at gmail dot com
Target Milestone: ---
Target: i?86-pc-solaris2.11, x86_64-pc-solaris2.11
The gcc.target/i386/avx512fp16-trunchf.c test has been FAILing on 32-bit
Solaris/x86
since it was installed:
FAIL: gcc.target/i386/avx512fp16-trunchf.c scan-assembler-times vcvttsh2si[
\\\\t]+[^{\\n]*(?:%xmm[0-9]|\\\\(%esp\\\\))+, %eax(?:\\n|[ \\\\t]+#) 3
FAIL: gcc.target/i386/avx512fp16-trunchf.c scan-assembler-times vcvttsh2usi[
\\\\t]+[^{\\n]*(?:%xmm[0-9]|\\\\(%esp\\\\))+, %eax(?:\\n|[ \\\\t]+#) 2
On Solaris, the assembler output contains
vcvttsh2si 8(%ebp), %eax
vcvttsh2si 8(%ebp), %eax
vcvttsh2si 8(%ebp), %eax
vcvttsh2usi 8(%ebp), %eax
vcvttsh2usi 8(%ebp), %eax
while Linux has
vcvttsh2si 4(%esp), %eax
vcvttsh2si 4(%esp), %eax
vcvttsh2si 4(%esp), %eax
vcvttsh2usi 4(%esp), %eax
vcvttsh2usi 4(%esp), %eax
As it turns out, the difference occurs because Solaris/x86 default to
-fno-omit-frame-pointer. With -fomit-frame-pointer added, the output matches.
I wonder what's the best way to handle the difference? Just add
-fomit-frame-pointer
to the testcase or allow for the %ebp vs. %esp difference?
next reply other threads:[~2021-10-19 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 11:41 ro at gcc dot gnu.org [this message]
2021-10-19 11:42 ` [Bug target/102835] " ro at gcc dot gnu.org
2021-10-19 13:13 ` wwwhhhyyy333 at gmail dot com
2021-10-25 13:54 ` [Bug testsuite/102835] " ro at gcc dot gnu.org
2021-10-26 12:28 ` cvs-commit at gcc dot gnu.org
2021-10-26 12:29 ` 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-102835-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).