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/94446] Bogus "type mismatch" with TYPE(c_ptr) and sizeof()
Date: Fri, 09 Apr 2021 22:14:58 +0000	[thread overview]
Message-ID: <bug-94446-4-5GdC8pPBIH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94446-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Created attachment 50541
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50541&action=edit
Draft patch

I wonder whether something like that would work.

The only known failure is gfortran.dg/gomp/use_device_ptr-1.f90 which fails as
instead of
  void * x;
  #pragma omp target data map(alloc:x)
the wrong
  #pragma omp target data map(alloc:*x) map(alloc:x [pointer assign, bias: 0])
is generated (ICE as sizeof 'void' does not make sense).
(Fix should be in the code block below 'case OMP_LIST_MAP:' in trans-openmp.c)

I wonder what else goes wrong with 'type(c_ptr)' and 'type(c_ptr),pointer'
besides this issue and the one 'fn spec' issue (already fixed in the attached
patch).

      parent reply	other threads:[~2021-04-09 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 16:05 [Bug fortran/94446] New: " abensonca at gcc dot gnu.org
2021-02-14 18:27 ` [Bug fortran/94446] " dominiq at lps dot ens.fr
2021-03-29 22:01 ` abensonca at gmail dot com
2021-04-09 22:14 ` burnus 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-94446-4-5GdC8pPBIH@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).