public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107127] [11 Regression] Long compile times on code with C complex since r11-3299-gcba079f354a55363 Date: Tue, 02 May 2023 20:12:09 +0000 [thread overview] Message-ID: <bug-107127-4-CivMBdg9Aq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107127-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107127 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:21d09955d2b7755db7d5ba3cd4a314930b470da7 commit r11-10682-g21d09955d2b7755db7d5ba3cd4a314930b470da7 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Nov 23 19:09:31 2022 +0100 c: Fix compile time hog in c_genericize [PR107127] The complex multiplications result in deeply nested set of many SAVE_EXPRs, which takes even on fast machines over 5 minutes to walk. This patch fixes that by using walk_tree_without_duplicates where it is instant. 2022-11-23 Andrew Pinski <apinski@marvell.com> Jakub Jelinek <jakub@redhat.com> PR c/107127 * c-gimplify.c (c_genericize): Use walk_tree_without_duplicates instead of walk_tree for c_genericize_control_r. * gcc.dg/pr107127.c: New test. (cherry picked from commit 8a0fce6a51915c29584427fd376b40073c328090)
next prev parent reply other threads:[~2023-05-02 20:12 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-03 2:03 [Bug c/107127] New: [Regression 11/12] Long compile times on code with C complex inform at tiker dot net 2022-10-03 9:31 ` [Bug c/107127] [11/12/13 Regression] Long compile times on code with C complex since r11-3299-gcba079f354a55363 marxin at gcc dot gnu.org 2022-10-03 9:53 ` marxin at gcc dot gnu.org 2022-10-03 19:49 ` pinskia at gcc dot gnu.org 2022-10-03 19:52 ` pinskia at gcc dot gnu.org 2022-10-06 9:59 ` rguenth at gcc dot gnu.org 2022-11-22 11:10 ` jakub at gcc dot gnu.org 2022-11-23 18:10 ` cvs-commit at gcc dot gnu.org 2022-11-23 18:11 ` [Bug c/107127] [11/12 " jakub at gcc dot gnu.org 2022-11-24 9:34 ` cvs-commit at gcc dot gnu.org 2023-02-10 17:43 ` cvs-commit at gcc dot gnu.org 2023-02-10 17:44 ` cvs-commit at gcc dot gnu.org 2023-02-10 17:57 ` [Bug c/107127] [11 " jakub at gcc dot gnu.org 2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org 2023-05-03 9:29 ` jakub 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-107127-4-CivMBdg9Aq@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).