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 tree-optimization/111820] [13 Regression] Compiler time hog in the vectorizer with `-O3 -fno-tree-vrp` Date: Fri, 27 Oct 2023 01:20:33 +0000 [thread overview] Message-ID: <bug-111820-4-zqqA3Nt5Z5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111820-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111820 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #16 from Andrew Pinski <pinskia at gcc dot gnu.org> --- .
next prev parent reply other threads:[~2023-10-27 1:20 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-15 2:02 [Bug c/111820] New: GCC: 14: hangs with a simple while loop 141242068 at smail dot nju.edu.cn 2023-10-15 2:07 ` [Bug tree-optimization/111820] " pinskia at gcc dot gnu.org 2023-10-15 2:09 ` [Bug tree-optimization/111820] [13/14 Regression] Compiler time hog in the vectorizer with `-O3 -fno-tree-vrp` pinskia at gcc dot gnu.org 2023-10-16 7:14 ` rguenth at gcc dot gnu.org 2023-10-16 7:22 ` crazylht at gmail dot com 2023-10-16 7:43 ` crazylht at gmail dot com 2023-10-16 8:46 ` rguenther at suse dot de 2023-10-17 6:56 ` crazylht at gmail dot com 2023-10-17 7:16 ` rguenther at suse dot de 2023-10-17 9:13 ` crazylht at gmail dot com 2023-10-17 9:47 ` rguenth at gcc dot gnu.org 2023-10-23 1:16 ` cvs-commit at gcc dot gnu.org 2023-10-23 2:39 ` crazylht at gmail dot com 2023-10-23 9:42 ` [Bug tree-optimization/111820] [13 " rguenth at gcc dot gnu.org 2023-10-27 1:06 ` cvs-commit at gcc dot gnu.org 2023-10-27 1:18 ` crazylht at gmail dot com 2023-10-27 1:20 ` pinskia at gcc dot gnu.org [this message] 2023-10-27 3:29 ` pinskia 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-111820-4-zqqA3Nt5Z5@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).