public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <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, Date: Mon, 15 Aug 2022 07:22:26 +0000 [thread overview] Message-ID: <bug-106617-4-JI9kfU1S9z@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 #6 from Sergei Trofimovich <slyfox at gcc dot gnu.org> --- Created attachment 53455 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53455&action=edit ring_buffer.c.gz ring_buffer.c.gz is a preprocessed file from linux-4.19. $ time gcc-12.1.0 -O2 -c ring_buffer.c -o bug.o real 0m0,308s user 0m0,285s sys 0m0,017s $ gcc -O2 -c ring_buffer.c -o bug.o # Runs for minutes, increases RAM usage, never finishes. perf stats after 3 minutes' run: 10,16% cc1 [.] operand_compare::operand_equal_p 7,38% cc1 [.] fold_binary_loc 7,01% cc1 [.] generic_simplify_453 5,63% cc1 [.] generic_simplify_GT_EXPR 3,72% cc1 [.] wide_int_binop 3,42% cc1 [.] generic_simplify_COND_EXPR 3,38% cc1 [.] hash_table<int_cst_hasher, false, xcallocator>::find_slot_with_hash 3,04% cc1 [.] wide_int_to_tree_1 3,00% cc1 [.] tree_strip_nop_conversions 2,82% cc1 [.] int_const_binop 2,47% cc1 [.] get_inner_reference 2,45% cc1 [.] fold_build2_loc 2,23% cc1 [.] fold_ternary_loc 2,07% cc1 [.] tree_strip_sign_nop_conversions 1,96% cc1 [.] int_cst_hasher::hash 1,83% cc1 [.] ggc_internal_alloc 1,81% cc1 [.] fold_relational_const 1,61% cc1 [.] wi::fits_to_tree_p<poly_int<1u, generic_wide_int<wide_int_ref_storage<false, true> > > > 1,57% cc1 [.] generic_simplify_155 1,51% cc1 [.] operand_equal_p 1,22% cc1 [.] dbg_cnt 1,20% cc1 [.] element_precision 1,10% cc1 [.] ggc_free
next prev parent reply other threads:[~2022-08-15 7:22 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-14 21:52 [Bug tree-optimization/106617] New: " 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 [this message] 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
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-JI9kfU1S9z@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).