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 tree-optimization/108482] [13 Regression] ice in expand_LOOP_DIST_ALIAS with -O3 -ftrivial-auto-var-init=zero Date: Sat, 21 Jan 2023 16:57:29 +0000 [thread overview] Message-ID: <bug-108482-4-cgIpAppeH9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108482-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108482 --- Comment #11 from David Binderman <dcb314 at hotmail dot com> --- It looks to me like g:af96500eea72c674a5686b35c66202ef2bd9688f is the culprit. Over to Richard for their best advice.
next prev parent reply other threads:[~2023-01-21 16:57 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-20 16:24 [Bug c/108482] New: ice in expand_LOOP_DIST_ALIAS, at internal-fn.cc:2737 dcb314 at hotmail dot com 2023-01-20 16:32 ` [Bug c/108482] " dcb314 at hotmail dot com 2023-01-20 21:13 ` [Bug tree-optimization/108482] [13 Regression] ice in expand_LOOP_DIST_ALIAS with -O3 -ftrivial-auto-var-init=zero pinskia at gcc dot gnu.org 2023-01-20 21:15 ` pinskia at gcc dot gnu.org 2023-01-20 21:19 ` pinskia at gcc dot gnu.org 2023-01-21 14:19 ` dcb314 at hotmail dot com 2023-01-21 14:20 ` dcb314 at hotmail dot com 2023-01-21 14:49 ` dcb314 at hotmail dot com 2023-01-21 15:18 ` dcb314 at hotmail dot com 2023-01-21 16:31 ` dcb314 at hotmail dot com 2023-01-21 16:52 ` dcb314 at hotmail dot com 2023-01-21 16:57 ` dcb314 at hotmail dot com [this message] 2023-01-21 20:13 ` pinskia at gcc dot gnu.org 2023-01-23 7:24 ` rguenth at gcc dot gnu.org 2023-01-23 10:51 ` cvs-commit at gcc dot gnu.org 2023-01-23 10: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-108482-4-cgIpAppeH9@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).