From: "sunil.k.pandey" <skpandey@sc.intel.com>
To: gcc-patches@gcc.gnu.org, gcc-regression@gcc.gnu.org, hubicka@ucw.cz
Subject: [r12-3159 Regression] FAIL: gfortran.dg/pr68251.f90 -O (test for excess errors) on Linux/x86_64
Date: Thu, 26 Aug 2021 10:50:54 -0700 [thread overview]
Message-ID: <20210826175054.7A4D02864700@gskx-2.sc.intel.com> (raw)
On Linux/x86_64,
f075b8c5adcf9cb6336563c472c8d624c54184db is the first bad commit
commit f075b8c5adcf9cb6336563c472c8d624c54184db
Author: Jan Hubicka <hubicka@ucw.cz>
Date: Thu Aug 26 15:33:56 2021 +0200
Fix off-by-one error in try_merge_with
caused
FAIL: gcc.c-torture/compile/960514-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (internal compiler error)
FAIL: gcc.c-torture/compile/960514-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: gcc.c-torture/compile/960514-1.c -O3 -g (internal compiler error)
FAIL: gcc.c-torture/compile/960514-1.c -O3 -g (test for excess errors)
FAIL: gcc.dg/vect/O3-pr45971.c (internal compiler error)
FAIL: gcc.dg/vect/O3-pr45971.c (test for excess errors)
FAIL: gfortran.dg/pr68251.f90 -O (internal compiler error)
FAIL: gfortran.dg/pr68251.f90 -O (test for excess errors)
with GCC configured with
To reproduce:
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="compile.exp=gcc.c-torture/compile/960514-1.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="compile.exp=gcc.c-torture/compile/960514-1.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="compile.exp=gcc.c-torture/compile/960514-1.c --target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/O3-pr45971.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/O3-pr45971.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/O3-pr45971.c --target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/pr68251.f90 --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/pr68251.f90 --target_board='unix{-m64\ -march=cascadelake}'"
(Please do not reply to this email, for question about this report, contact me at skpgkp2 at gmail dot com)
next reply other threads:[~2021-08-26 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 17:50 sunil.k.pandey [this message]
2021-08-28 7:39 sunil.k.pandey
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=20210826175054.7A4D02864700@gskx-2.sc.intel.com \
--to=skpandey@sc.intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=hubicka@ucw.cz \
/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).