public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/103496] [F2018][TS29113] C_SIZEOF – rejects now valid args with 'must be an interoperable data entity'
Date: Fri, 12 Apr 2024 08:59:27 +0000 [thread overview]
Message-ID: <bug-103496-4-G1qVZ0J0ip@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103496-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103496
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to anlauf from comment #3)
> The code in comment#0 compiles at r14-9893-gded646c91d2c0f
> and gives the indicated results.
which is the commit:
Fortran: fix argument checking of intrinsics C_SIZEOF, C_F_POINTER [PR106500]
It looks as if the issue is fixed, but gfortran misses a tescast to check that
the obtained value is correct.
c_sizeof_7.f90 contains tests, but I think there should be a run time trst that
the obtained values are correct; I think some are constants such that a
tree-dump scan test would work as well, but for the dynamic ones, a run time
test seems zo be easier than trying to capture the generated code...
next prev parent reply other threads:[~2024-04-12 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 13:54 [Bug fortran/103496] New: " burnus at gcc dot gnu.org
2021-11-30 20:14 ` [Bug fortran/103496] " anlauf at gcc dot gnu.org
2021-11-30 21:02 ` burnus at gcc dot gnu.org
2024-04-10 17:19 ` anlauf at gcc dot gnu.org
2024-04-12 8:59 ` burnus at gcc dot gnu.org [this message]
2024-04-12 19:18 ` anlauf at gcc dot gnu.org
2024-04-23 18:25 ` cvs-commit at gcc dot gnu.org
2024-04-23 18:28 ` 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-103496-4-G1qVZ0J0ip@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).