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/102836] New: gcc.target/i386/pieces-memset-1.c etc. FAIL
Date: Tue, 19 Oct 2021 11:56:10 +0000 [thread overview]
Message-ID: <bug-102836-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102836
Bug ID: 102836
Summary: gcc.target/i386/pieces-memset-1.c etc. FAIL
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: hjl.tools at gmail dot com
Target Milestone: ---
Target: i?86-pc-solaris2.11, x86_64-pc-solaris2.11
Some gcc.target/i386/pieces-memset-*.c tests have been FAILing on 32-bit
Solaris/x86
since they were installed:
FAIL: gcc.target/i386/pieces-memset-1.c scan-assembler-not %[re]bp
FAIL: gcc.target/i386/pieces-memset-4.c scan-assembler-not %[re]bp
FAIL: gcc.target/i386/pieces-memset-41.c scan-assembler-not %[re]bp
FAIL: gcc.target/i386/pieces-memset-7.c scan-assembler-not %[re]bp
FAIL: gcc.target/i386/pieces-memset-8.c scan-assembler-not %[re]bp
It turns out that this happens because 32-bit Solaris/x86 only guarantees
4-byte stack alignment following the i386 psABI, so defaults to -mstackrealign.
Adding -mno-stackrealign to one test lets the output match what I get on
Linux/x86. I suspect that's the best option?
next reply other threads:[~2021-10-19 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 11:56 ro at gcc dot gnu.org [this message]
2021-10-19 11:56 ` [Bug target/102836] " ro at gcc dot gnu.org
2021-10-19 12:26 ` hjl.tools at gmail dot com
2021-10-25 13:47 ` [Bug testsuite/102836] " ro at gcc dot gnu.org
2021-10-26 12:21 ` cvs-commit at gcc dot gnu.org
2021-10-26 12:21 ` 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-102836-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).