public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104391] [11 Regression] bind(C) and allocatable or pointer attribute don't work
Date: Thu, 25 Apr 2024 06:20:40 +0000 [thread overview]
Message-ID: <bug-104391-4-JAVFyF0PWF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104391-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104391
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #2)
> Fixed on master with r12-2511-g0cbf03689e3e7d9d, started with
> r9-5372-gbbf18dc5d248a79a.
Yes, indeed.
Thanks, Martin.
prev parent reply other threads:[~2024-04-25 6:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 20:45 [Bug fortran/104391] New: Gfortran 9 regression with bind(C) and allocatable or pointer attribute michael at scivision dot dev
2022-02-04 21:34 ` [Bug fortran/104391] [9/10/11 Regression] bind(C) and allocatable or pointer attribute don't work pinskia at gcc dot gnu.org
2022-02-05 3:14 ` pinskia at gcc dot gnu.org
2022-02-07 7:47 ` rguenth at gcc dot gnu.org
2022-02-22 10:51 ` marxin at gcc dot gnu.org
2022-05-27 9:47 ` [Bug fortran/104391] [10/11 " rguenth at gcc dot gnu.org
2022-06-28 10:48 ` jakub at gcc dot gnu.org
2023-07-07 10:42 ` [Bug fortran/104391] [11 " rguenth at gcc dot gnu.org
2024-04-25 6:20 ` pault at gcc dot gnu.org [this message]
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-104391-4-JAVFyF0PWF@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).