From: Mike Stump <mikestump@comcast.net>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gcc-patches@gcc.gnu.org, Roger Sayle <roger@nextmovesoftware.com>
Subject: Re: [PATCH] testsuite: i386: Fix gcc.target/i386/pr70321.c on 32-bit Solaris/x86
Date: Thu, 1 Feb 2024 16:10:11 -0800 [thread overview]
Message-ID: <D85793FC-7957-4123-84B8-0B0228510632@comcast.net> (raw)
In-Reply-To: <ydd7cjz14xb.fsf@CeBiTec.Uni-Bielefeld.DE>
On Jan 24, 2024, at 1:01 AM, Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> wrote:
>
> gcc.target/i386/pr70321.c FAILs on 32-bit Solaris/x86 since its
> introduction in
>
> commit 43201f2c2173894bf7c423cad6da1c21567e06c0
> Author: Roger Sayle <roger@nextmovesoftware.com>
> Date: Mon May 30 21:20:09 2022 +0100
>
> PR target/70321: Split double word equality/inequality after STV on x86.
>
> FAIL: gcc.target/i386/pr70321.c scan-assembler-times mov 1
>
> The failure happens because 32-bit Solaris/x86 defaults to
> -fno-omit-frame-pointer.
>
> Fixed by specifying -fomit-frame-pointer explicitly.
>
> Tested on i386-pc-solaris2.11 and i686-pc-linux-gnu.
>
> Ok for trunk?
Ok.
prev parent reply other threads:[~2024-02-02 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 9:01 Rainer Orth
2024-02-02 0:10 ` Mike Stump [this message]
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=D85793FC-7957-4123-84B8-0B0228510632@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=roger@nextmovesoftware.com \
/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).