public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/111263] New: test case gfortran.dg/ieee/comparisons_3.F90 fails Date: Thu, 31 Aug 2023 21:57:36 +0000 [thread overview] Message-ID: <bug-111263-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111263 Bug ID: 111263 Summary: test case gfortran.dg/ieee/comparisons_3.F90 fails Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- make -k check-fortran RUNTESTFLAGS="--target_board=unix'{-m32,m64}' ieee.exp=gfortran.dg/ieee/comparisons_3.F90" FAIL: gfortran.dg/ieee/comparisons_3.F90 -O0 execution test FAIL: gfortran.dg/ieee/comparisons_3.F90 -O1 execution test FAIL: gfortran.dg/ieee/comparisons_3.F90 -O2 execution test FAIL: gfortran.dg/ieee/comparisons_3.F90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gfortran.dg/ieee/comparisons_3.F90 -O3 -g execution test FAIL: gfortran.dg/ieee/comparisons_3.F90 -Os execution test I can't definitely trace it to a specific commit because of build errors but I believe it has failed since its introduction here: commit dca2874897ec58ea1c22a9c2161f112fff07cfb2 (HEAD) Author: Francois-Xavier Coudert <fxcoudert@gcc.gnu.org> Date: Fri Sep 2 13:27:38 2022 +0200 Fortran: add IEEE_QUIET_* and IEEE_SIGNALING_* comparisons * gfortran.dg/ieee/comparisons_3.F90: New test. The failure is at line 46: spawn [open ...] Check failed at 46 STOP 1 FAIL: gfortran.dg/ieee/comparisons_3.F90 -Os execution test if (ieee_signaling_eq (0., rnan)) stop 13 CHECK_INVALID(.true.)
next reply other threads:[~2023-08-31 21:57 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-31 21:57 seurer at gcc dot gnu.org [this message] 2023-08-31 22:04 ` [Bug target/111263] " pinskia at gcc dot gnu.org 2023-09-07 14:56 ` seurer at gcc dot gnu.org
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=bug-111263-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).