public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/101135] Load of null pointer when passing absent assumed-shape array argument for an optional dummy argument
Date: Sat, 23 Mar 2024 20:13:12 +0000 [thread overview]
Message-ID: <bug-101135-4-IN8iXD3M0K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101135-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101135
--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:344b60addb79278c95b7a5712aaf381111721a27
commit r13-8492-g344b60addb79278c95b7a5712aaf381111721a27
Author: Harald Anlauf <anlauf@gmx.de>
Date: Fri Mar 15 20:14:07 2024 +0100
Fortran: fix for absent array argument passed to optional dummy [PR101135]
gcc/fortran/ChangeLog:
PR fortran/101135
* trans-array.cc (gfc_get_dataptr_offset): Check for optional
arguments being present before dereferencing data pointer.
gcc/testsuite/ChangeLog:
PR fortran/101135
* gfortran.dg/missing_optional_dummy_6a.f90: Adjust diagnostic
pattern.
* gfortran.dg/ubsan/missing_optional_dummy_8.f90: New test.
next prev parent reply other threads:[~2024-03-23 20:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 12:49 [Bug fortran/101135] New: Use of absent assumed-shape array argument as an actual argument for an optional dummy argument mistakenly flagged as error by UndefinedBehaviourSanitizer marcel.jacobse at ewetel dot net
2021-06-26 1:07 ` [Bug fortran/101135] " marcel.jacobse at ewetel dot net
2021-06-26 13:20 ` marcel.jacobse at ewetel dot net
2022-01-27 20:38 ` [Bug fortran/101135] Load of null pointer when passing absent assumed-shape array argument for an optional dummy argument anlauf at gcc dot gnu.org
2022-01-28 22:22 ` anlauf at gcc dot gnu.org
2022-01-29 21:43 ` anlauf at gcc dot gnu.org
2022-01-31 20:49 ` anlauf at gcc dot gnu.org
2024-03-17 21:42 ` cvs-commit at gcc dot gnu.org
2024-03-23 20:13 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-23 20:14 ` anlauf at gcc dot gnu.org
2024-03-23 21:01 ` marcel.jacobse at ewetel dot net
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-101135-4-IN8iXD3M0K@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).