public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/113685] New: [14 regression] xxx fails after yyy
Date: Wed, 31 Jan 2024 18:42:16 +0000 [thread overview]
Message-ID: <bug-113685-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113685
Bug ID: 113685
Summary: [14 regression] xxx fails after yyy
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:d45ddc2c04e471d0dcee016b6edacc00b8341b16, r14-4089-gd45ddc2c04e471
make -k check-gcc RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-117.c"
FAIL: gcc.dg/vect/vect-117.c scan-tree-dump-not optimized "Invalid sum"
FAIL: gcc.dg/vect/vect-117.c -flto -ffat-lto-objects scan-tree-dump-not
optimized "Invalid sum"
# of expected passes 8
# of unexpected failures 2
Note this was also reported in pr111462 but the fix for it did not fix this
failure.
commit d45ddc2c04e471d0dcee016b6edacc00b8341b16 (HEAD)
Author: Richard Biener <rguenther@suse.de>
Date: Thu Sep 14 13:06:51 2023 +0200
tree-optimization/111294 - backwards threader PHI costing
* gcc.dg/vect/vect-117.c: Make scan for not Invalid sum
conditional on lp64.
next reply other threads:[~2024-01-31 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 18:42 seurer at gcc dot gnu.org [this message]
2024-02-01 7:40 ` [Bug testsuite/113685] [14 regression] gcc.dg/vect/vect-117.c fails profile checking with Invalid sum after r14-4089-gd45ddc2c04e471 rguenth at gcc dot gnu.org
2024-02-28 15:21 ` 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@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).