public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/106041] [12/13 Regression] infinite loop in fast_dce at -O1 with aarch64 Date: Tue, 21 Feb 2023 19:42:00 +0000 [thread overview] Message-ID: <bug-106041-4-f1mMOzVpkD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106041-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106041 --- Comment #13 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (insn 42 41 43 3 (clobber (reg/v:V4x1DF 40 v8 [orig:96 tup ] [96])) -1 (nil))
next prev parent reply other threads:[~2023-02-21 19:42 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-21 6:03 [Bug c++/106041] New: Long/infinite compile time for Arm SIMD -O1 or -O2 but not -O0 jan.wassenberg at gmail dot com 2022-06-21 6:19 ` [Bug rtl-optimization/106041] " pinskia at gcc dot gnu.org 2022-06-21 6:26 ` [Bug rtl-optimization/106041] infinite loop in fast_dce at -O1 with aarch64 pinskia at gcc dot gnu.org 2022-06-21 6:28 ` pinskia at gcc dot gnu.org 2022-06-21 7:05 ` jan.wassenberg at gmail dot com 2022-06-21 8:52 ` [Bug rtl-optimization/106041] [12/13 Regression] " rguenth at gcc dot gnu.org 2022-06-21 9:02 ` marxin at gcc dot gnu.org 2022-06-21 9:20 ` jan.wassenberg at gmail dot com 2022-06-21 9:20 ` jan.wassenberg at gmail dot com 2022-09-05 13:32 ` malat at debian dot org 2023-02-21 14:52 ` rguenth at gcc dot gnu.org 2023-02-21 19:29 ` rguenth at gcc dot gnu.org 2023-02-21 19:33 ` rguenth at gcc dot gnu.org 2023-02-21 19:42 ` pinskia at gcc dot gnu.org [this message] 2023-02-21 19:43 ` pinskia at gcc dot gnu.org 2023-02-21 19:44 ` pinskia at gcc dot gnu.org 2023-02-21 19:46 ` pinskia at gcc dot gnu.org 2023-02-22 8:53 ` 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-106041-4-f1mMOzVpkD@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).