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 libfortran/106079] New: [12/13 regression] gfortran.dg/boz_15.f90 fails after gcc-12-6498-g07c60b8e33 Date: Fri, 24 Jun 2022 12:24:02 +0000 [thread overview] Message-ID: <bug-106079-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106079 Bug ID: 106079 Summary: [12/13 regression] gfortran.dg/boz_15.f90 fails after gcc-12-6498-g07c60b8e33 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:07c60b8e33c614a6cdd9fe3de7f409319b6a239a, gcc-12-6498-g07c60b8e33 make -k check-gcc-fortran RUNTESTFLAGS="dg.exp=gfortran.dg/boz_15.f90" FAIL: gfortran.dg/boz_15.f90 -O0 execution test FAIL: gfortran.dg/boz_15.f90 -O1 execution test FAIL: gfortran.dg/boz_15.f90 -O2 execution test FAIL: gfortran.dg/boz_15.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gfortran.dg/boz_15.f90 -O3 -g execution test FAIL: gfortran.dg/boz_15.f90 -Os execution test # of expected passes 6 # of unexpected failures 6 commit 07c60b8e33c614a6cdd9fe3de7f409319b6a239a (HEAD) Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Jan 4 10:37:48 2022 +0100 fortran, libgfortran: -mabi=ieeelongdouble I/O At line 20 of file /home/seurer/gcc/git/gcc-12-test/gcc/testsuite/gfortran.dg/boz_15.f90 Fortran runtime error: Bad value during integer read Error termination. Backtrace: #0 0x7fffa583af03 in formatted_transfer_scalar_read at /home/seurer/gcc/git/gcc-12-test/libgfortran/io/transfer.c:1513 #1 0x7fffa583c307 in formatted_transfer at /home/seurer/gcc/git/gcc-12-test/libgfortran/io/transfer.c:2339 #2 0x7fffa5836f47 in wrap_scalar_transfer at /home/seurer/gcc/git/gcc-12-test/libgfortran/io/transfer.c:2382 #3 0x100104d3 in ??? #4 0x10010ce3 in ??? #5 0x7fffa5237f2b in ??? #6 0x7fffa5238107 in ??? #7 0xffffffffffffffff in ??? FAIL: gfortran.dg/boz_15.f90 -O0 execution test This occurs with the compiler configured with --with-long-double-format=ieee on a distro (Fedora 36) which also used --with-long-double-format=ieee.
next reply other threads:[~2022-06-24 12:24 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-24 12:24 seurer at gcc dot gnu.org [this message] 2022-06-24 12:53 ` [Bug libfortran/106079] " rguenth at gcc dot gnu.org 2022-07-25 15:52 ` [Bug libfortran/106079] [12/13 regression] gfortran.dg/boz_15.f90 fails after r12-6498-g07c60b8e33 rguenth at gcc dot gnu.org 2022-07-29 14:35 ` jakub at gcc dot gnu.org 2022-07-29 20:58 ` seurer at gcc dot gnu.org 2022-07-30 2:49 ` seurer at gcc dot gnu.org 2022-07-30 10:46 ` jakub at gcc dot gnu.org 2022-07-30 11:19 ` jakub at gcc dot gnu.org 2022-08-01 6:26 ` cvs-commit at gcc dot gnu.org 2022-08-01 22:07 ` seurer at gcc dot gnu.org 2022-08-03 9:22 ` cvs-commit at gcc dot gnu.org 2022-08-03 9:24 ` jakub 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-106079-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).