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 rtl-optimization/102627] [11 Regression] wrong code with "-O1"
Date: Thu, 14 Oct 2021 16:11:51 +0000	[thread overview]
Message-ID: <bug-102627-4-P7uXGvxPEd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102627-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Vladimir Makarov
<vmakarov@gcc.gnu.org>:

https://gcc.gnu.org/g:99d21577f8a00196f3133fe1066de6e3e7d180c1

commit r11-9154-g99d21577f8a00196f3133fe1066de6e3e7d180c1
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date:   Fri Oct 8 10:16:09 2021 -0400

    [PR102627] Use at least natural mode during splitting hard reg live range

    In the PR test case SImode was used to split live range of cx on x86-64
    because it was the biggest mode for this hard reg in the function.  But
    all 64-bits of cx contain structure members.  We need always to use at
least
    natural mode of hard reg in splitting to fix this problem.

    gcc/ChangeLog:

            PR rtl-optimization/102627
            * lra-constraints.c (split_reg): Use at least natural mode of hard
reg.

    gcc/testsuite/ChangeLog:

            PR rtl-optimization/102627
            * gcc.target/i386/pr102627.c: New test.

  parent reply	other threads:[~2021-10-14 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06  8:37 [Bug tree-optimization/102627] New: " suochenyao at 163 dot com
2021-10-06 10:13 ` [Bug tree-optimization/102627] " rguenth at gcc dot gnu.org
2021-10-06 10:32 ` [Bug rtl-optimization/102627] [11/12 Regression] " jakub at gcc dot gnu.org
2021-10-06 10:42 ` jakub at gcc dot gnu.org
2021-10-07 19:54 ` vmakarov at gcc dot gnu.org
2021-10-08 16:54 ` cvs-commit at gcc dot gnu.org
2021-10-11  8:32 ` [Bug rtl-optimization/102627] [11 " jakub at gcc dot gnu.org
2021-10-14 16:11 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-14 16:15 ` vmakarov at gcc dot gnu.org
2021-10-22 20:11 ` hjl.tools at gmail 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-102627-4-P7uXGvxPEd@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).