From: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com>
To: dizhao@os.amperecomputing.com, gcc-regression@gcc.gnu.org,
gcc-patches@gcc.gnu.org, haochen.jiang@intel.com
Subject: [r14-6559 Regression] FAIL: gcc.dg/guality/pr58791-4.c -Os -DPREVENT_OPTIMIZATION line pr58791-4.c:32 i == 486 on Linux/x86_64
Date: Sat, 16 Dec 2023 01:36:18 +0800 [thread overview]
Message-ID: <202312151736.3BFHaITp3548555@shliclel4214.sh.intel.com> (raw)
On Linux/x86_64,
8afdbcdd7abe1e3c7a81e07f34c256e7f2dbc652 is the first bad commit
commit 8afdbcdd7abe1e3c7a81e07f34c256e7f2dbc652
Author: Di Zhao <dizhao@os.amperecomputing.com>
Date: Fri Dec 15 03:22:32 2023 +0800
Consider fully pipelined FMA in get_reassociation_width
caused
FAIL: gcc.dg/pr110279-2.c scan-tree-dump-not reassoc2 "was chosen for reassociation"
FAIL: gcc.dg/pr110279-2.c scan-tree-dump-times optimized "\\.FMA " 3
with GCC configured with
../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-6559/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap
To reproduce:
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/pr110279-2.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/pr110279-2.c --target_board='unix{-m64}'"
(Please do not reply to this email, for question about this report, contact me at haochen dot jiang at intel.com)
(If you met problems with cascadelake related, disabling AVX512F in command line might save that.)
(However, please make sure that there is no potential problems with AVX512.)
next reply other threads:[~2023-12-15 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 17:36 haochen.jiang [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-15 1:23 haochen.jiang
2023-12-15 8:06 ` Richard Biener
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=202312151736.3BFHaITp3548555@shliclel4214.sh.intel.com \
--to=haochenj@ecsmtp.sh.intel.com \
--cc=dizhao@os.amperecomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=haochen.jiang@intel.com \
/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).