public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/113685] [14 regression] gcc.dg/vect/vect-117.c fails profile checking with Invalid sum after r14-4089-gd45ddc2c04e471
Date: Thu, 01 Feb 2024 07:40:46 +0000	[thread overview]
Message-ID: <bug-113685-4-BW9VdSsJLT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113685-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2024-02-01
                 CC|                            |hubicka at gcc dot gnu.org
     Ever confirmed|0                           |1
   Target Milestone|---                         |14.0
           Keywords|                            |testsuite-fail
            Summary|[14 regression] xxx fails   |[14 regression]
                   |after yyy                   |gcc.dg/vect/vect-117.c
                   |                            |fails profile checking with
                   |                            |Invalid sum after
                   |                            |r14-4089-gd45ddc2c04e471
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
As said in the other PR, this is more for Honza who thought checking we do not
end with invalid profiles for all vect testcases is a good thing ;)

Btw, the wrong count pops up in DOM3:

t.c.203t.dom3:;;   Invalid sum of incoming counts 138435014 (estimated locally,
freq 3.0936), should be 134239200 (estimated locally, freq 2.9999)

so it seems to be a jump threading issue.  It's gone with -fno-thread-jumps.

Very likely a latent issue, but of course the change triggering this does
have an effect on jump threading.

Confirmed.

  reply	other threads:[~2024-02-01  7:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 18:42 [Bug testsuite/113685] New: [14 regression] xxx fails after yyy seurer at gcc dot gnu.org
2024-02-01  7:40 ` rguenth at gcc dot gnu.org [this message]
2024-02-28 15:21 ` [Bug testsuite/113685] [14 regression] gcc.dg/vect/vect-117.c fails profile checking with Invalid sum after r14-4089-gd45ddc2c04e471 ro at gcc dot gnu.org
2024-02-28 15:22 ` ro at gcc dot gnu.org
2024-03-07 20:42 ` law at gcc dot gnu.org
2024-05-07  7:44 ` [Bug testsuite/113685] [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-113685-4-BW9VdSsJLT@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).