public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112374] [14 Regression] Failed bootstrap with `--with-arch=skylake-avx512 --with-cpu=skylake-avx512`, causes a comparison failure since r14-5076-g01c18f58d37865d5f3bbe93e666183b54ec
Date: Wed, 15 Nov 2023 19:51:14 +0000 [thread overview]
Message-ID: <bug-112374-4-obpFPDjI1M@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112374-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #23 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #22)
> This one starts to differ during RTL expansion, -fdump-tree-optimized
> differs only
> with addition of DEBUG stmts, but expand dump already has:
> -(insn 1007 1006 1008 (parallel [
> +(insn 1007 8 1008 (parallel [
> (set (reg:DI 106)
> (plus:DI (reg/f:DI 93 virtual-stack-vars)
> - (const_int -32 [0xffffffffffffffe0])))
> + (const_int -4 [0xfffffffffffffffc])))
> (clobber (reg:CC 17 flags))
> ]) "pr112374.C":11:14 -1
> (nil))
That looks like a different issue than the original though. I am getting the
feeling we are going to find a lot of compare debug issues with this one
testcase.
next prev parent reply other threads:[~2023-11-15 19:51 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 0:59 [Bug target/112374] New: --with-arch=native bootstrap is broken on `Xeon(R) D-2166NT` pinskia at gcc dot gnu.org
2023-11-04 1:48 ` [Bug target/112374] " pinskia at gcc dot gnu.org
2023-11-04 2:06 ` [Bug target/112374] [14 Regression] " pinskia at gcc dot gnu.org
2023-11-04 2:50 ` pinskia at gcc dot gnu.org
2023-11-04 4:01 ` [Bug target/112374] [14 Regression] `--with-arch=skylake-avx512 --with-cpu=skylake-avx512` causes a comparison failure pinskia at gcc dot gnu.org
2023-11-04 5:19 ` pinskia at gcc dot gnu.org
2023-11-08 2:06 ` haochen.jiang at intel dot com
2023-11-08 8:51 ` rdapp at gcc dot gnu.org
2023-11-08 12:22 ` crazylht at gmail dot com
2023-11-09 1:02 ` pinskia at gcc dot gnu.org
2023-11-10 7:36 ` crazylht at gmail dot com
2023-11-14 10:18 ` crazylht at gmail dot com
2023-11-14 10:21 ` rdapp at gcc dot gnu.org
2023-11-14 10:30 ` crazylht at gmail dot com
2023-11-14 17:04 ` pinskia at gcc dot gnu.org
2023-11-15 6:22 ` [Bug target/112374] [14 Regression] Failed bootstrap with `--with-arch=skylake-avx512 --with-cpu=skylake-avx512`, " sjames at gcc dot gnu.org
2023-11-15 12:05 ` [Bug target/112374] [14 Regression] Failed bootstrap with `--with-arch=skylake-avx512 --with-cpu=skylake-avx512`, causes a comparison failure since r14-5076-g01c18f58d37865d5f3bbe93e666183b54ec rguenth at gcc dot gnu.org
2023-11-15 12:45 ` jakub at gcc dot gnu.org
2023-11-15 17:15 ` jakub at gcc dot gnu.org
2023-11-15 17:57 ` pinskia at gcc dot gnu.org
2023-11-15 18:07 ` jakub at gcc dot gnu.org
2023-11-15 18:38 ` jakub at gcc dot gnu.org
2023-11-15 18:50 ` pinskia at gcc dot gnu.org
2023-11-15 19:31 ` jakub at gcc dot gnu.org
2023-11-15 19:34 ` jakub at gcc dot gnu.org
2023-11-15 19:51 ` pinskia at gcc dot gnu.org [this message]
2023-11-15 19:52 ` pinskia at gcc dot gnu.org
2023-11-15 20:37 ` jakub at gcc dot gnu.org
2023-11-15 20:50 ` jakub at gcc dot gnu.org
2023-11-15 21:08 ` jakub at gcc dot gnu.org
2023-11-15 21:33 ` jakub at gcc dot gnu.org
2023-11-15 21:46 ` jakub at gcc dot gnu.org
2023-11-16 6:25 ` pinskia at gcc dot gnu.org
2023-11-16 6:40 ` [Bug tree-optimization/112374] " pinskia at gcc dot gnu.org
2023-11-16 6:47 ` pinskia at gcc dot gnu.org
2023-11-16 6:49 ` rguenther at suse dot de
2023-11-16 8:31 ` rdapp at gcc dot gnu.org
2023-11-16 9:03 ` rdapp at gcc dot gnu.org
2023-11-16 9:08 ` jakub at gcc dot gnu.org
2023-11-16 9:12 ` jakub at gcc dot gnu.org
2023-11-16 9:22 ` jakub at gcc dot gnu.org
2023-11-16 9:36 ` jakub at gcc dot gnu.org
2023-11-16 9:38 ` rdapp at gcc dot gnu.org
2023-11-16 9:43 ` rguenth at gcc dot gnu.org
2023-11-16 9:47 ` pinskia at gcc dot gnu.org
2023-11-16 9:52 ` jakub at gcc dot gnu.org
2023-11-16 9:53 ` jakub at gcc dot gnu.org
2023-11-16 9:55 ` pinskia at gcc dot gnu.org
2023-11-16 10:26 ` rdapp at gcc dot gnu.org
2023-11-16 19:38 ` rdapp at gcc dot gnu.org
2023-11-17 14:11 ` cvs-commit at gcc dot gnu.org
2023-11-17 14:12 ` jakub 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-112374-4-obpFPDjI1M@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).