public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/114211] [13/14 Regression] wrong code with -O -fno-tree-coalesce-vars
Date: Mon, 04 Mar 2024 15:00:35 +0000	[thread overview]
Message-ID: <bug-114211-4-qHFi7JatVi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114211-4@http.gcc.gnu.org/bugzilla/>

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

Uroš Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|target                      |rtl-optimization
           Keywords|needs-bisection             |

--- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Richard Biener from comment #2)
> Possibly target independent rtl-optimization issue.

It is _subreg1 pass that converts:

(insn 10 7 11 2 (set (reg/v:TI 106 [ h ])
        (rotate:TI (reg/v:TI 106 [ h ])
            (const_int 64 [0x40]))) "pr114211.c":9:5 1042
{rotl64ti2_doubleword}
     (nil))

to:

(insn 39 7 40 2 (set (reg:DI 128 [ h+8 ])
        (reg:DI 127 [ h ])) "pr114211.c":9:5 84 {*movdi_internal}
     (nil))
(insn 40 39 11 2 (set (reg:DI 127 [ h ])
        (reg:DI 128 [ h+8 ])) "pr114211.c":9:5 84 {*movdi_internal}
     (nil))

Well... this won't swap. Either parallel should be emitted, or a temporary
should be used.

Adding -fno-split-wide-types fixes the testcase.

Re-confirmed as rtl-optimization problem.

  parent reply	other threads:[~2024-03-04 15:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02 19:03 [Bug tree-optimization/114211] New: " zsojka at seznam dot cz
2024-03-02 20:59 ` [Bug target/114211] " pinskia at gcc dot gnu.org
2024-03-04 10:08 ` rguenth at gcc dot gnu.org
2024-03-04 15:00 ` ubizjak at gmail dot com [this message]
2024-03-04 18:32 ` [Bug rtl-optimization/114211] [13/14 Regression] wrong code with -O -fno-tree-coalesce-vars since r13-1907 jakub at gcc dot gnu.org
2024-03-04 18:59 ` jakub at gcc dot gnu.org
2024-03-04 19:41 ` jakub at gcc dot gnu.org
2024-03-05  9:33 ` cvs-commit at gcc dot gnu.org
2024-03-05  9:38 ` [Bug rtl-optimization/114211] [13 " jakub at gcc dot gnu.org
2024-03-05 11:35 ` ubizjak at gmail dot com
2024-03-15 23:29 ` cvs-commit at gcc dot gnu.org
2024-03-18 14:41 ` jakub 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-114211-4-qHFi7JatVi@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).