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/106122] [12/13 Regression] ICE in fixup_args_size_notes,  at expr.cc:4493 since r12-6106-gef26c151c14a8717
Date: Sun, 03 Jul 2022 13:02:26 +0000	[thread overview]
Message-ID: <bug-106122-4-7WzQVDbKz8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106122-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:

https://gcc.gnu.org/g:55899e33de74082521708a58fdc79510e0c5efad

commit r12-8542-g55899e33de74082521708a58fdc79510e0c5efad
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Sun Jul 3 14:01:17 2022 +0100

    PR target/106122: Don't update %esp via the stack with -Oz on x86.

    When optimizing for size with -Oz, setting a register can be minimized by
    pushing an immediate value to the stack and popping it to the destination.
    Alas the one general register that shouldn't be updated via the stack is
    the stack pointer itself, where "pop %esp" can't be represented in GCC's
    RTL ("use of a register mentioned in pre_inc, pre_dec, post_inc or
    post_dec is not permitted within the same instruction").  This patch
    fixes PR target/106122 by explicitly checking for SP_REG in the
    problematic peephole2.

    2022-07-O3  Roger Sayle  <roger@nextmovesoftware.com>

    gcc/ChangeLog
            PR target/106122
            * config/i386/i386.md (peephole2): Avoid generating pop %esp
            when optimizing for size.

    gcc/testsuite/ChangeLog
            PR target/106122
            * gcc.target/i386/pr106122.c: New test case.

  parent reply	other threads:[~2022-07-03 13:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 17:06 [Bug c/106122] New: [12/13 Regression] ICE in fixup_args_size_notes, at expr.cc:4493 gscfq@t-online.de
2022-06-29  9:44 ` [Bug target/106122] " rguenth at gcc dot gnu.org
2022-06-29 12:05 ` [Bug target/106122] [12/13 Regression] ICE in fixup_args_size_notes, at expr.cc:4493 since r12-6106-gef26c151c14a8717 marxin at gcc dot gnu.org
2022-06-29 13:03 ` roger at nextmovesoftware dot com
2022-07-01  8:20 ` cvs-commit at gcc dot gnu.org
2022-07-03 13:02 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-03 13:23 ` roger at nextmovesoftware dot com

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-106122-4-7WzQVDbKz8@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).