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/108961] Segfault when associating to pointer from C_F_POINTER
Date: Wed, 21 Jun 2023 16:02:09 +0000 [thread overview]
Message-ID: <bug-108961-4-MinE1Zghtl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108961-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108961
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Paul Thomas <pault@gcc.gnu.org>:
https://gcc.gnu.org/g:caf0892eea67349d9a1e44590c3440768136fe2b
commit r14-2021-gcaf0892eea67349d9a1e44590c3440768136fe2b
Author: Paul Thomas <pault@gcc.gnu.org>
Date: Wed Jun 21 17:01:57 2023 +0100
Fortran: Seg fault passing string to type cptr dummy [PR108961].
2023-06-21 Paul Thomas <pault@gcc.gnu.org>
gcc/fortran
PR fortran/108961
* trans-expr.cc (gfc_conv_procedure_call): The hidden string
length must not be passed to a formal arg of type(cptr).
gcc/testsuite/
PR fortran/108961
* gfortran.dg/pr108961.f90: New test.
next prev parent reply other threads:[~2023-06-21 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 0:22 [Bug fortran/108961] New: " jeffrey.p.hill at nasa dot gov
2023-02-28 0:23 ` [Bug fortran/108961] " jeffrey.p.hill at nasa dot gov
2023-03-23 18:39 ` pault at gcc dot gnu.org
2023-04-18 9:17 ` pault at gcc dot gnu.org
2023-06-20 12:55 ` pault at gcc dot gnu.org
2023-06-21 16:02 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-21 21:07 ` pault at gcc dot gnu.org
2023-07-29 20:18 ` anlauf at gcc dot gnu.org
2023-07-30 9:46 ` paul.richard.thomas at gmail dot com
2023-07-30 12:25 ` cvs-commit 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-108961-4-MinE1Zghtl@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).