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/104819] Reject NULL without MOLD as actual to an assumed-rank dummy
Date: Tue, 08 Mar 2022 07:31:52 +0000	[thread overview]
Message-ID: <bug-104819-4-UPq0iGGoZz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104819-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104819

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #0)
> I believe this should be rejected as the rank is not known without a MOLD.

That's now an interpretation request:
https://j3-fortran.org/doc/year/22/22-146.txt

(Note: might see updates, such as 22-146r1.txt or ...)

 * * *

In the email thread, also an issue related to C_SIZEOF was mentioned:
https://j3-fortran.org/doc/year/22/22-101r1.txt

Example from the IR, see IR for details about the validity.

program p
 use iso_c_binding
 implicit none
 integer(c_int), pointer :: int_s
 integer(c_int), pointer :: int_a(:)
 print *, c_sizeof (c_null_ptr) ! (A)
 print *, c_sizeof (null ())    ! (B)
 print *, c_sizeof (null (int_s)) ! (C)
 print *, c_sizeof (null (int_a)) ! (D)
end

  reply	other threads:[~2022-03-08  7:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 13:24 [Bug fortran/104819] New: " burnus at gcc dot gnu.org
2022-03-08  7:31 ` burnus at gcc dot gnu.org [this message]
2023-11-06 20:32 ` [Bug fortran/104819] " anlauf at gcc dot gnu.org
2023-11-06 20:46 ` anlauf at gcc dot gnu.org
2023-11-09 21:32 ` anlauf at gcc dot gnu.org
2023-11-12 21:02 ` anlauf at gcc dot gnu.org
2023-11-14 21:17 ` anlauf at gcc dot gnu.org
2023-11-16 20:19 ` anlauf at gcc dot gnu.org
2023-11-23 18:32 ` cvs-commit at gcc dot gnu.org
2024-02-29 21:01 ` anlauf at gcc dot gnu.org
2024-03-01 18:22 ` cvs-commit at gcc dot gnu.org
2024-03-15 21:08 ` cvs-commit at gcc dot gnu.org
2024-03-15 21:08 ` 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-104819-4-UPq0iGGoZz@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).