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 fortran/113621] New: New test case gfortran.dg/optional_absent_10.f90 from r14-8400-g186ae6d2cb93ad fails
Date: Fri, 26 Jan 2024 20:06:58 +0000 [thread overview]
Message-ID: <bug-113621-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113621
Bug ID: 113621
Summary: New test case gfortran.dg/optional_absent_10.f90 from
r14-8400-g186ae6d2cb93ad fails
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:186ae6d2cb93ad2e07117cff7e11def21fe285ae, r14-8400-g186ae6d2cb93ad
make -k check-gcc-fortran RUNTESTFLAGS="--target_board=unix'{-m32,-m64}'
dg.exp=gfortran.dg/optional_absent_10.f90"
FAIL: gfortran.dg/optional_absent_10.f90 -O0 execution test
# of expected passes 11
# of expected passes 12
# of expected passes 23
# of unexpected failures 1
# of unexpected failures 1
This appears to be a problem just on big endian.
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0xf7f803f3 in ???
#1 0x10000c68 in __m_char_MOD_three_val
at
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/optional_absent_10.f90:97
#2 0x10001bcb in __m_char_MOD_test_char
at
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/optional_absent_10.f90:19
#3 0x1000269b in p
at
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/optional_absent_10.f90:218
#4 0x100026f3 in main
at
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/optional_absent_10.f90:214
Segmentation fault
commit 186ae6d2cb93ad2e07117cff7e11def21fe285ae (HEAD)
Author: Harald Anlauf <anlauf@gmx.de>
Date: Wed Jan 24 20:27:36 2024 +0100
Fortran: passing of optional dummies to elemental procedures [PR113377]
next reply other threads:[~2024-01-26 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 20:06 seurer at gcc dot gnu.org [this message]
2024-01-26 20:33 ` [Bug fortran/113621] " anlauf at gcc dot gnu.org
2024-01-26 21:00 ` anlauf 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-113621-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: 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).