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 target/110649] [14 Regression] 25% sphinx3 spec2006 regression on Ice Lake and zen between g:acaa441a98bebc52 (2023-07-06 11:36) and g:55900189ab517906 (2023-07-07 00:23) Date: Sun, 16 Jul 2023 21:54:23 +0000 [thread overview] Message-ID: <bug-110649-4-TssO5ReKFe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110649-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110649 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jan Hubicka <hubicka@gcc.gnu.org>: https://gcc.gnu.org/g:1d203d4c90adb064edfa9680768d1f83a41f17e0 commit r14-2544-g1d203d4c90adb064edfa9680768d1f83a41f17e0 Author: Jan Hubicka <jh@suse.cz> Date: Sun Jul 16 23:53:56 2023 +0200 Avoid double profile udpate in try_peel_loop try_peel_loop uses gimple_duplicate_loop_body_to_header_edge which subtracts the profile from the original loop. However then it tries to scale the profile in a wrong way (it forces header count to be entry count). This eliminates to profile misupdates in the internal loop of sphinx3. gcc/ChangeLog: PR middle-end/110649 * tree-ssa-loop-ivcanon.cc (try_peel_loop): Avoid double profile update.
next prev parent reply other threads:[~2023-07-16 21:54 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-12 22:35 [Bug target/110649] New: " hubicka at gcc dot gnu.org 2023-07-12 22:39 ` [Bug target/110649] " pinskia at gcc dot gnu.org 2023-07-12 22:39 ` [Bug target/110649] [14 Regression] " pinskia at gcc dot gnu.org 2023-07-14 7:16 ` hliu at amperecomputing dot com 2023-07-14 14:39 ` hubicka at gcc dot gnu.org 2023-07-14 14:41 ` hubicka at gcc dot gnu.org 2023-07-16 16:25 ` hubicka at gcc dot gnu.org 2023-07-16 17:39 ` hubicka at gcc dot gnu.org 2023-07-16 20:06 ` hubicka at gcc dot gnu.org 2023-07-16 20:14 ` hubicka at gcc dot gnu.org 2023-07-16 21:54 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-16 21:55 ` cvs-commit at gcc dot gnu.org 2023-07-16 21:57 ` cvs-commit at gcc dot gnu.org 2023-07-17 10:48 ` roger at nextmovesoftware dot com 2023-07-17 11:53 ` jamborm at gcc dot gnu.org 2023-07-18 14:49 ` hubicka at gcc dot gnu.org 2023-07-18 15:56 ` [Bug target/110649] [14 Regression] 25% sphinx3 spec2006 regression on Ice Lake and zen since g:r14-2369-g3a61ca1b925653 (2023-07-06) hubicka at gcc dot gnu.org 2024-03-07 23:29 ` law at gcc dot gnu.org 2024-05-07 7:41 ` [Bug target/110649] [14/15 " 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-110649-4-TssO5ReKFe@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).