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 target/110758] [14 Regression] 8% hmmer regression on zen1/3 with -Ofast -march=native -flto between g:8377cf1bf41a0a9d (2023-07-05 01:46) and g:3a61ca1b9256535e (2023-07-06 16:56); g:d76d19c9bc5ef113 (2023-07-16 00:16) and g:a5088dc3f5ef73c8 (2023-07-17 03:24)
Date: Wed, 26 Jul 2023 12:19:00 +0000	[thread overview]
Message-ID: <bug-110758-4-6B1srUtM4d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110758-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110758

Jan Hubicka <hubicka at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2023-07-26
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #3 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Regression between  
  g:d76d19c9bc5ef113 (2023-07-16 00:16) and 
  g:a5088dc3f5ef73c8 (2023-07-17 03:24)  
seems to be gone. 


The range is:
  1c6231c05bdccab3 (2023-07-21 03:06) and
  f33fdf9e7c038639 (2023-07-23 00:17)

Looking at the patches in range, it is likely the flat profile detection in 
vectorizer:

Author: Jan Hubicka <jh@suse.cz>
Date:   Fri Jul 21 19:38:26 2023 +0200

    Avoid scaling flat loop profiles of vectorized loops

  parent reply	other threads:[~2023-07-26 12:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 22:02 [Bug target/110758] New: 8% hmmer regression on zen1 and zen3 with -Ofast -march=native -flto between g:8377cf1bf41a0a9d (2023-07-05 01:46) and g:3a61ca1b9256535e (2023-07-06 16:56) and " hubicka at gcc dot gnu.org
2023-07-20 22:12 ` [Bug target/110758] [14 Regression] 8% hmmer regression on zen1/3 with -Ofast -march=native -flto between g:8377cf1bf41a0a9d (2023-07-05 01:46) and g:3a61ca1b9256535e (2023-07-06 16:56); " pinskia at gcc dot gnu.org
2023-07-20 22:13 ` pinskia at gcc dot gnu.org
2023-07-21 17:13   ` Jan Hubicka
2023-07-21 17:13 ` hubicka at ucw dot cz
2023-07-26 12:19 ` hubicka at gcc dot gnu.org [this message]
2023-07-31  7:39 ` hubicka 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-110758-4-6B1srUtM4d@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).