public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/70321] [10/11/12/13 Regression] STV generates less optimized code
Date: Thu, 01 Feb 2024 11:49:29 +0000	[thread overview]
Message-ID: <bug-70321-4-NSUjq717RF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-70321-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70321

--- Comment #27 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Rainer Orth <ro@gcc.gnu.org>:

https://gcc.gnu.org/g:ee7011eab67d8272f88e954bbab2e42bf6353441

commit r14-8690-gee7011eab67d8272f88e954bbab2e42bf6353441
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date:   Thu Feb 1 12:48:57 2024 +0100

    testsuite: i386: Fix gcc.target/i386/pr70321.c on 32-bit Solaris/x86

    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.

    2024-01-23  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>

            gcc/testsuite:
            * gcc.target/i386/pr70321.c: Add -fomit-frame-pointer to
            dg-options.

      parent reply	other threads:[~2024-02-01 11:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-70321-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` [Bug target/70321] [8/9/10 " jakub at gcc dot gnu.org
2021-06-01  8:07 ` [Bug target/70321] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-04-19 13:09 ` roger at nextmovesoftware dot com
2022-05-27  9:36 ` [Bug target/70321] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-05-30 20:21 ` cvs-commit at gcc dot gnu.org
2022-06-04  9:12 ` roger at nextmovesoftware dot com
2024-02-01 11:49 ` cvs-commit at gcc dot gnu.org [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=bug-70321-4-NSUjq717RF@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).