public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com>
To: tamar.christina@arm.com, gcc-regression@gcc.gnu.org,
	gcc-patches@gcc.gnu.org, haochen.jiang@intel.com
Subject: [r14-9969 Regression] FAIL: gcc.dg/vect/vect-early-break_124-pr114403.c -flto -ffat-lto-objects execution test on Linux/x86_64
Date: Tue, 16 Apr 2024 03:04:52 +0800	[thread overview]
Message-ID: <202404151904.43FJ4q5N1747744@shliclel4214.sh.intel.com> (raw)

On Linux/x86_64,

85002f8085c25bb3e74ab013581a74e7c7ae006b is the first bad commit
commit 85002f8085c25bb3e74ab013581a74e7c7ae006b
Author: Tamar Christina <tamar.christina@arm.com>
Date:   Mon Apr 15 12:06:21 2024 +0100

    middle-end: adjust loop upper bounds when peeling for gaps and early break [PR114403].

caused

FAIL: gcc.dg/vect/vect-early-break_124-pr114403.c execution test
FAIL: gcc.dg/vect/vect-early-break_124-pr114403.c -flto -ffat-lto-objects execution test

with GCC configured with

../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-9969/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="vect.exp=gcc.dg/vect/vect-early-break_124-pr114403.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-early-break_124-pr114403.c --target_board='unix{-m32\ -march=cascadelake}'"

(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.)

                 reply	other threads:[~2024-04-15 19:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202404151904.43FJ4q5N1747744@shliclel4214.sh.intel.com \
    --to=haochenj@ecsmtp.sh.intel.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=haochen.jiang@intel.com \
    --cc=tamar.christina@arm.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).