public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: Hongtao Liu <crazylht@gmail.com>
To: "sunil.k.pandey" <skpandey@sc.intel.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	gcc-regression@gcc.gnu.org,  "Liu,
	Hongtao" <hongtao.liu@intel.com>
Subject: Re: [r12-4240 Regression] FAIL: libgomp.c++/scan-9.C scan-tree-dump-times vect "vectorized [2-6] loops" 2 on Linux/x86_64
Date: Sat, 9 Oct 2021 10:57:56 +0800	[thread overview]
Message-ID: <CAMZc-bw66mer8bHL-jYCQ8kWznx6x4U735k6y0UKer+-1pYV1w@mail.gmail.com> (raw)
In-Reply-To: <CAMZc-bwyuV-nrWc1CoSxXQYFtSG6EPvr9gMNUrq7Ui53tjuxyQ@mail.gmail.com>

On Sat, Oct 9, 2021 at 10:53 AM Hongtao Liu <crazylht@gmail.com> wrote:
>
> On Sat, Oct 9, 2021 at 1:27 AM sunil.k.pandey via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
> >
> > On Linux/x86_64,
> >
> > 2b8453c401b699ed93c085d0413ab4b5030bcdb8 is the first bad commit
> > commit 2b8453c401b699ed93c085d0413ab4b5030bcdb8
> > Author: liuhongt <hongtao.liu@intel.com>
> > Date:   Mon Sep 6 13:48:49 2021 +0800
> >
> >     Enable auto-vectorization at O2 with very-cheap cost model.
> >
> > caused
> >
> > FAIL: gcc.dg/optimize-bswapsi-5.c scan-tree-dump-times optimized "= __builtin_bswap32 \\(" 2
> > FAIL: gcc.dg/optimize-bswapsi-6.c scan-tree-dump store-merging "32 bit bswap implementation found at"
> > FAIL: gcc.dg/torture/pr69760.c   -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects  (test for excess errors)
> Those testcase should be adjusted with either add -fno-tree-vectorize
> or add -mtune=generic when target is x86 except for runtime test
> pr69760.c which seems to be a real bug.
Oh, it's not runtime failure, its extra warning message after vectorization.

/export/users2/liuhongt/gcc/intel-innersource/O2_vectorization/gcc/testsuite/gcc.dg/torture/pr69760.c:
In function 'test_func':
/export/users2/liuhongt/gcc/intel-innersource/O2_vectorization/gcc/testsuite/gcc.dg/torture/pr69760.c:16:10:
warning: iteration 54 invokes undefined behavior
[-Waggressive-loop-optimizations]
/export/users2/liuhongt/gcc/intel-innersource/O2_vectorization/gcc/testsuite/gcc.dg/torture/pr69760.c:12:17:
note: within this loop

> > FAIL: gcc.dg/Warray-bounds-51.c  target { i?86-*-* x86_64-*-* }  (test for warnings, line 41)
> > FAIL: gcc.dg/Wstringop-overflow-14.c  target { i?86-*-* x86_64-*-* }  (test for warnings, line 38)
> > FAIL: g++.dg/tree-ssa/pr94403.C   scan-tree-dump-times store-merging "__builtin_bswap32" 1
> > FAIL: g++.dg/tree-ssa/pr94403.C   scan-tree-dump-times store-merging "__builtin_bswap64" 1
> >
> > with GCC configured with
> >
> > ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-4240/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/optimize-bswapsi-5.c --target_board='unix{-m64\ -march=cascadelake}'"
> > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/optimize-bswapsi-6.c --target_board='unix{-m32\ -march=cascadelake}'"
> > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/optimize-bswapsi-6.c --target_board='unix{-m64\ -march=cascadelake}'"
> > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg-torture.exp=gcc.dg/torture/pr69760.c --target_board='unix{-m32\ -march=cascadelake}'"
> > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Warray-bounds-51.c --target_board='unix{-m32\ -march=cascadelake}'"
> > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Warray-bounds-51.c --target_board='unix{-m64\ -march=cascadelake}'"
> > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wstringop-overflow-14.c --target_board='unix{-m32\ -march=cascadelake}'"
> > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wstringop-overflow-14.c --target_board='unix{-m64\ -march=cascadelake}'"
> > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/tree-ssa/pr94403.C --target_board='unix{-m64\ -march=cascadelake}'"
> > $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/lastprivate-conditional-7.c --target_board='unix{-m32}'"
> > $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/lastprivate-conditional-7.c --target_board='unix{-m32\ -march=cascadelake}'"
> > $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/lastprivate-conditional-7.c --target_board='unix{-m64}'"
> > $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/lastprivate-conditional-7.c --target_board='unix{-m64\ -march=cascadelake}'"
> > $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/lastprivate-conditional-8.c --target_board='unix{-m32}'"
> > $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/lastprivate-conditional-8.c --target_board='unix{-m32\ -march=cascadelake}'"
> > $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/lastprivate-conditional-8.c --target_board='unix{-m64}'"
> > $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/lastprivate-conditional-8.c --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)
>
>
>
> --
> BR,
> Hongtao



-- 
BR,
Hongtao


  reply	other threads:[~2021-10-09  2:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 17:27 sunil.k.pandey
2021-10-09  2:53 ` Hongtao Liu
2021-10-09  2:57   ` Hongtao Liu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-08 12:01 sunil.k.pandey
2021-10-09  2:52 ` Hongtao Liu

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=CAMZc-bw66mer8bHL-jYCQ8kWznx6x4U735k6y0UKer+-1pYV1w@mail.gmail.com \
    --to=crazylht@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=hongtao.liu@intel.com \
    --cc=skpandey@sc.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).