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/112560] [14 Regression] ICE in try_combine on pr112494.c
Date: Mon, 11 Mar 2024 11:54:51 +0000	[thread overview]
Message-ID: <bug-112560-4-7LSNbHrNMN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112560-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #56705|0                           |1
        is obsolete|                            |

--- Comment #5 from Uroš Bizjak <ubizjak at gmail dot com> ---
Created attachment 57666
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57666&action=edit
Proposed v2 patch

New version of patch in testing.

This version handles change of the mode of CC reg outside comparison. Now we
scan the RTX and change the mode of the CC reg at the proper place. We are
guaranteed by find_single_use that cc_use_loc can be non-NULL only when exactly
one user follows the combined comparison.

In case of unsupported cc_use_insn combine will be undone. To avoid combine
failure, pushfl<mode>2 in i386.md is changed to accept all MODE_CC modes.

  parent reply	other threads:[~2024-03-11 11:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16  7:23 [Bug middle-end/112560] New: " jakub at gcc dot gnu.org
2023-11-16  7:24 ` [Bug middle-end/112560] [14 Regression] " jakub at gcc dot gnu.org
2023-11-18  6:17 ` pinskia at gcc dot gnu.org
2023-11-18  6:17 ` pinskia at gcc dot gnu.org
2023-11-28 16:00 ` ubizjak at gmail dot com
2023-11-28 17:33 ` ubizjak at gmail dot com
2023-11-29  9:37 ` ubizjak at gmail dot com
2024-03-11 11:54 ` ubizjak at gmail dot com [this message]
2024-03-12 17:54 ` [Bug rtl-optimization/112560] " ubizjak at gmail dot com
2024-04-08 20:22 ` cvs-commit at gcc dot gnu.org
2024-04-09  8:26 ` rguenth at gcc dot gnu.org
2024-04-09  8:28 ` ubizjak at gmail dot com
2024-04-10 17:55 ` segher at gcc dot gnu.org
2024-04-10 18:34 ` ubizjak at gmail dot com
2024-04-10 22:44 ` segher at gcc dot gnu.org
2024-04-11  6:33 ` ubizjak 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-112560-4-7LSNbHrNMN@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).