public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/102842] [10 Regression] ICE in cselib_record_set at -O2 or greater
Date: Wed, 20 Oct 2021 12:19:01 +0000	[thread overview]
Message-ID: <bug-102842-4-f9ckV0KHKJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102842-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to tt_1 from comment #7)
> hey, thanks for the messages. I just finished to compile firefox with
> patched cross-gcc-10.3.0, the ice is fixed with the patch from
> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;
> h=74dc179a6da33cd00f6d4a93fbb97dc84f610126 applied to it. 

Great!

> 
> So can you please tell me if this has already been backported to the gcc-10
> branch?

No, it wasn't.

> I just browsed through the git dirs, and I'm not certain. Also no
> hint in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92807 that its been
> fixed for the gcc-10 branch. 
> 
> Is it queued to be backported?

Apparently, the commit does not fix a regression so the author decided not to
backport it.

So I would recommend updating to GCC 11.2.0, which is the latest support
release.

> Sorry if I'm asking dumb questions, I'm just
> a regular user, not a gentoo dev.

No, your questions are very reasonable and we thank you reporting the issue you
deal with.

  parent reply	other threads:[~2021-10-20 12:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 14:43 [Bug other/102842] New: [10 Regression] ICE in cselib_record_set at 02 " herrtimson at yahoo dot de
2021-10-19 14:43 ` [Bug other/102842] " herrtimson at yahoo dot de
2021-10-19 14:50 ` marxin at gcc dot gnu.org
2021-10-19 14:55 ` herrtimson at yahoo dot de
2021-10-19 18:36 ` [Bug rtl-optimization/102842] " pinskia at gcc dot gnu.org
2021-10-19 18:43 ` [Bug rtl-optimization/102842] [10/11/12 " pinskia at gcc dot gnu.org
2021-10-20  8:28 ` [Bug rtl-optimization/102842] [10 Regression] ICE in cselib_record_set at -O2 " marxin at gcc dot gnu.org
2021-10-20 10:46 ` marxin at gcc dot gnu.org
2021-10-20 10:46 ` marxin at gcc dot gnu.org
2021-10-20 11:32 ` herrtimson at yahoo dot de
2021-10-20 12:19 ` marxin at gcc dot gnu.org [this message]
2021-10-20 15:29 ` herrtimson at yahoo dot de
2021-10-21  7:25 ` marxin at gcc dot gnu.org
2021-10-21 12:35 ` herrtimson at yahoo dot de
2021-10-21 17:47 ` vmakarov at gcc dot gnu.org
2021-10-26 19:17 ` cvs-commit at gcc dot gnu.org
2021-10-30 10:32 ` [Bug rtl-optimization/102842] [10/11/12 " herrtimson at yahoo dot de
2021-11-03 17:47 ` cvs-commit at gcc dot gnu.org
2021-11-03 17:48 ` cvs-commit at gcc dot gnu.org
2021-11-05 13:51 ` rguenth 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-102842-4-f9ckV0KHKJ@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).