public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105856] [13 Regression] ice in emit_move_insn, at expr.cc:4011 Date: Thu, 09 Jun 2022 11:50:12 +0000 [thread overview] Message-ID: <bug-105856-4-HS7EhwxC8X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105856-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105856 --- Comment #7 from David Binderman <dcb314 at hotmail dot com> --- (In reply to Roger Sayle from comment #6) > Hi David. Thanks again for all your help (building Linux distributions is a > helpful/vital service to the GCC community). Thanks. Good to know I am doing something useful. 820 bugs in 10+ years. >Can you confirm that this problem is now fixed on ARM? I just confirmed that today's gcc compiler (git hash 2fc6e3d55f6080da) has it fixed. Much thanks for your fast work on this bug report. Found & fixed in four days.
next prev parent reply other threads:[~2022-06-09 11:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-05 13:10 [Bug target/105856] New: " dcb314 at hotmail dot com 2022-06-05 13:15 ` [Bug target/105856] " dcb314 at hotmail dot com 2022-06-05 21:31 ` [Bug target/105856] [13 Regression] " roger at nextmovesoftware dot com 2022-06-06 13:52 ` roger at nextmovesoftware dot com 2022-06-06 17:02 ` dcb314 at hotmail dot com 2022-06-07 9:13 ` cvs-commit at gcc dot gnu.org 2022-06-09 11:15 ` roger at nextmovesoftware dot com 2022-06-09 11:50 ` dcb314 at hotmail dot com [this message] 2022-06-09 13:37 ` roger at nextmovesoftware 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-105856-4-HS7EhwxC8X@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: linkBe 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).