public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/110757] [14 Regression] 7% parest regression on zen3 -Ofast -march=native -flto between g:4dbb3af1efe55174 (2023-07-14 00:54) and g:a5088dc3f5ef73c8 (2023-07-17 03:24) Date: Wed, 26 Jul 2023 07:15:27 +0000 [thread overview] Message-ID: <bug-110757-4-8ImUUQkVxO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110757-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110757 --- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Most of the profile based regression is gone between g:1c6231c05bdccab3 (2023-07-21 03:06) and g:f33fdf9e7c038639 (2023-07-23 00:17) This should be: commit a31ef26b056d0c4f0a9f08b6eb81456ea257298e Author: Jan Hubicka <jh@suse.cz> Date: Fri Jul 21 19:38:26 2023 +0200 Avoid scaling flat loop profiles of vectorized loops Which "fixes" the overactive scaling of scale_profile_for_vect_loop for static profiles. Still not sure why propagating profile later causes regression - will take a look.
next prev parent reply other threads:[~2023-07-26 7:15 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-20 21:55 [Bug middle-end/110757] New: " hubicka at gcc dot gnu.org 2023-07-20 21:58 ` [Bug middle-end/110757] [14 Regression] " pinskia at gcc dot gnu.org 2023-07-21 17:17 ` jamborm at gcc dot gnu.org 2023-07-21 19:14 ` jamborm at gcc dot gnu.org 2023-07-22 11:41 ` jamborm at gcc dot gnu.org 2023-07-26 7:15 ` hubicka at gcc dot gnu.org [this message] 2024-03-07 23:28 ` law at gcc dot gnu.org 2024-05-07 7:41 ` [Bug middle-end/110757] [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-110757-4-8ImUUQkVxO@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).