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/103722] [12 Regression] ICE in extract_constrain_insn building glibc for SH4
Date: Fri, 01 Jul 2022 15:27:51 +0000	[thread overview]
Message-ID: <bug-103722-4-9y8OSM73we@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103722-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Joseph Myers
<jsm28@gcc.gnu.org>:

https://gcc.gnu.org/g:962e7f0803f163f9cf44d64a2e199935d3f361fe

commit r12-8536-g962e7f0803f163f9cf44d64a2e199935d3f361fe
Author: Vladimir Makarov <vmakarov@gcc.gnu.org>
Date:   Sat May 28 12:08:38 2022 -0600

    Fix ICE on sh

    gcc/
            PR target/103722
            * config/sh/sh.cc (sh_register_move_cost): Avoid cost "2" (which
            is special) for various scenarios.

    (cherry picked from commit ce1580252ea57de23a595e9804ea87ed4353aa6a)

  parent reply	other threads:[~2022-07-01 15:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15  1:03 [Bug target/103722] New: " jsm28 at gcc dot gnu.org
2021-12-15  1:08 ` [Bug target/103722] " pinskia at gcc dot gnu.org
2021-12-15 20:43 ` vmakarov at gcc dot gnu.org
2022-01-04 11:17 ` rguenth at gcc dot gnu.org
2022-01-05 20:54 ` law at gcc dot gnu.org
2022-05-06  8:32 ` [Bug target/103722] [12/13 " jakub at gcc dot gnu.org
2022-05-08  9:05 ` mikpelinux at gmail dot com
2022-05-28 18:14 ` cvs-commit at gcc dot gnu.org
2022-05-28 18:16 ` law at gcc dot gnu.org
2022-07-01 15:27 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-01 15:28 ` [Bug target/103722] [12 " jsm28 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-103722-4-9y8OSM73we@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).