public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pivanov at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106617] [13 Regression] gcc is very slow at ternary expressions since r13-322-g7f04b0d786e13ff5
Date: Tue, 16 Aug 2022 15:10:00 +0000 [thread overview]
Message-ID: <bug-106617-4-oNom6qH2Qz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106617-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106617
--- Comment #11 from pivanov at hotmail dot com ---
(In reply to Martin Liška from comment #9)
> Started with r13-322-g7f04b0d786e13ff5.
I do confirm that after reverting this commit there is no more hanging when
compiling (bug 106642)
prev parent reply other threads:[~2022-08-16 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 21:52 [Bug tree-optimization/106617] New: [13 Regression] gcc is very slow at ternary expressions, slyfox at gcc dot gnu.org
2022-08-14 21:55 ` [Bug tree-optimization/106617] " pinskia at gcc dot gnu.org
2022-08-14 22:02 ` slyfox at gcc dot gnu.org
2022-08-14 22:08 ` slyfox at gcc dot gnu.org
2022-08-14 22:09 ` pinskia at gcc dot gnu.org
2022-08-15 7:01 ` slyfox at gcc dot gnu.org
2022-08-15 7:22 ` slyfox at gcc dot gnu.org
2022-08-15 7:39 ` pinskia at gcc dot gnu.org
2022-08-15 8:55 ` rguenth at gcc dot gnu.org
2022-08-15 9:06 ` rguenth at gcc dot gnu.org
2022-08-16 6:47 ` [Bug tree-optimization/106617] [13 Regression] gcc is very slow at ternary expressions since r13-322-g7f04b0d786e13ff5 marxin at gcc dot gnu.org
2022-08-16 7:17 ` rguenth at gcc dot gnu.org
2022-08-16 14:48 ` pinskia at gcc dot gnu.org
2022-08-16 15:10 ` pivanov at hotmail 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-106617-4-oNom6qH2Qz@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).