public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/111922] [11/12/13/14 Regression] ICE in cp with -O2 -fno-tree-fre
Date: Thu, 30 Nov 2023 18:31:09 +0000	[thread overview]
Message-ID: <bug-111922-4-78hQPrOJYj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111922-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from Andrew Macleod <amacleod at redhat dot com> ---
Created attachment 56735
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56735&action=edit
patch

(In reply to Sam James from comment #12)
> Is the plan to backport to 11/12/13 or to leave it?

hmm. I don't think I would apply the same patch  (it wouldn't work as is
anyway), but if we wanted to fix this in earlier releases we could simply have
the custom fold_ranges return false when the precision doesn't match...  it
would at least avoid most of these traps in earlier releases...?

The attached patch for instance would probably apply to GCC 13, 12 and 11..   
I  can test these if we want to do that...

      parent reply	other threads:[~2023-11-30 18:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22 16:38 [Bug c/111922] New: GCC: internal compiler error: in decompose, at wide-int.h:1049 141242068 at smail dot nju.edu.cn
2023-10-22 16:39 ` [Bug c/111922] " 141242068 at smail dot nju.edu.cn
2023-10-22 16:41 ` [Bug ipa/111922] [11/12/13/14 Regression] ICE in cp with -O2 -fno-tree-fre pinskia at gcc dot gnu.org
2023-10-23 16:51 ` jamborm at gcc dot gnu.org
2023-11-22 14:27 ` jakub at gcc dot gnu.org
2023-11-22 16:25 ` amacleod at redhat dot com
2023-11-22 16:32 ` jakub at gcc dot gnu.org
2023-11-22 17:29 ` amacleod at redhat dot com
2023-11-22 17:34 ` jakub at gcc dot gnu.org
2023-11-22 17:42 ` amacleod at redhat dot com
2023-11-29 16:51 ` cvs-commit at gcc dot gnu.org
2023-11-29 16:52 ` amacleod at redhat dot com
2023-11-29 23:22 ` sjames at gcc dot gnu.org
2023-11-30 18:31 ` amacleod at redhat dot com [this message]

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-111922-4-78hQPrOJYj@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).