public inbox for gcc-regression@sourceware.org help / color / mirror / Atom feed
From: "sunil.k.pandey" <skpandey@sc.intel.com> To: gcc-patches@gcc.gnu.org, gcc-regression@gcc.gnu.org, rguenther@suse.de Subject: [r12-6844 Regression] FAIL: gcc.dg/vect/pr81196.c scan-tree-dump-times vect "vectorized 1 loops" 1 on Linux/x86_64 Date: Mon, 24 Jan 2022 11:02:23 -0800 [thread overview] Message-ID: <20220124190223.78CB02864701@gskx-2.sc.intel.com> (raw) On Linux/x86_64, f1af8528d34418bc874ae9d993ee0dc3559972d2 is the first bad commit commit f1af8528d34418bc874ae9d993ee0dc3559972d2 Author: Richard Biener <rguenther@suse.de> Date: Mon Jan 24 11:50:06 2022 +0100 tree-optimization/102131 - fix niter analysis wrt overflow caused FAIL: gcc.dg/vect/pr81196.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorized 1 loops" 1 FAIL: gcc.dg/vect/pr81196.c scan-tree-dump-times vect "vectorized 1 loops" 1 with GCC configured with ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-6844/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/pr81196.c --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/pr81196.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)
reply other threads:[~2022-01-24 19:02 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=20220124190223.78CB02864701@gskx-2.sc.intel.com \ --to=skpandey@sc.intel.com \ --cc=gcc-patches@gcc.gnu.org \ --cc=gcc-regression@gcc.gnu.org \ --cc=rguenther@suse.de \ /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: linkBe 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).