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, fxcoudert@gcc.gnu.org Subject: [r12-6615 Regression] FAIL: gfortran.dg/ieee/signaling_2.f90 -Os execution test on Linux/x86_64 Date: Sun, 16 Jan 2022 17:53:47 -0800 [thread overview] Message-ID: <20220117015347.D44AA2864701@gskx-2.sc.intel.com> (raw) On Linux/x86_64, 90045c5df5b3c8853e7740fb72a11aead1c489bb is the first bad commit commit 90045c5df5b3c8853e7740fb72a11aead1c489bb Author: Francois-Xavier Coudert <fxcoudert@gcc.gnu.org> Date: Mon Jan 10 17:04:34 2022 +0100 Fortran: allow IEEE_VALUE to correctly return signaling NaNs caused FAIL: gfortran.dg/ieee/signaling_2.f90 -O0 execution test FAIL: gfortran.dg/ieee/signaling_2.f90 -O1 execution test FAIL: gfortran.dg/ieee/signaling_2.f90 -O2 execution test FAIL: gfortran.dg/ieee/signaling_2.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gfortran.dg/ieee/signaling_2.f90 -O3 -g execution test FAIL: gfortran.dg/ieee/signaling_2.f90 -Os execution test with GCC configured with ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-6615/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="ieee.exp=gfortran.dg/ieee/signaling_2.f90 --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="ieee.exp=gfortran.dg/ieee/signaling_2.f90 --target_board='unix{-m32\ -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-17 1:53 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=20220117015347.D44AA2864701@gskx-2.sc.intel.com \ --to=skpandey@sc.intel.com \ --cc=fxcoudert@gcc.gnu.org \ --cc=gcc-patches@gcc.gnu.org \ --cc=gcc-regression@gcc.gnu.org \ /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).