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 lto/114662] New: [14 regression] new test case c_lto_pr113359-2 from r14-9841-g1e3312a25a7b34 fails
Date: Tue, 09 Apr 2024 18:22:02 +0000 [thread overview]
Message-ID: <bug-114662-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114662
Bug ID: 114662
Summary: [14 regression] new test case c_lto_pr113359-2 from
r14-9841-g1e3312a25a7b34 fails
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:1e3312a25a7b34d6e3f549273e1674c7114e4408, r14-9841-g1e3312a25a7b34
I am seeing this on our big endian machines for -m32
make -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32}' lto.exp=*"
FAIL: gcc-dg-lto-pr113359-2-01.exe scan-wpa-ipa-dump icf "Semantic equality
hit:geta/.*getb/"
FAIL: gcc.dg/lto/pr113359-2 c_lto_pr113359-2_0.o assemble, -O2 -flto
-fno-strict-aliasing -fno-ipa-cp --disable-tree-esra -fdump-ipa-icf-details
FAIL: gcc.dg/lto/pr113359-2 c_lto_pr113359-2_0.o-c_lto_pr113359-2_1.o execute
-O2 -flto -fno-strict-aliasing -fno-ipa-cp --disable-tree-esra
-fdump-ipa-icf-details
commit 1e3312a25a7b34d6e3f549273e1674c7114e4408 (HEAD)
Author: Martin Jambor <mjambor@suse.cz>
Date: Mon Apr 8 18:53:23 2024 +0200
ICF&SRA: Make ICF and SRA agree on padding
next reply other threads:[~2024-04-09 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 18:22 seurer at gcc dot gnu.org [this message]
2024-04-09 18:54 ` [Bug lto/114662] " ewlu at rivosinc dot com
2024-04-10 5:56 ` linkw at gcc dot gnu.org
2024-04-10 6:26 ` [Bug testsuite/114662] " linkw at gcc dot gnu.org
2024-04-10 8:01 ` cvs-commit at gcc dot gnu.org
2024-04-10 8:04 ` linkw at gcc dot gnu.org
2024-04-10 9:24 ` jamborm at gcc dot gnu.org
2024-05-21 15:47 ` cvs-commit 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-114662-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).