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/49479] [4.6/4.7 Regression] reshape / optionals / zero sized arrays
Date: Tue, 21 Jun 2011 09:30:00 -0000	[thread overview]
Message-ID: <bug-49479-4-r1U7ch1BPs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49479-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49479

--- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-06-21 09:30:32 UTC ---
Actually, thinking about it: "RESHAPE(allocatable_array, shape)" is *not*
allocatable.

trans-expr.c has:
 147   if (!sym->attr.pointer && !sym->attr.allocatable
 148       && sym->as && sym->as->type == AS_ASSUMED_SHAPE
 149       && (gfc_option.allow_std & GFC_STD_F2008) != 0)

One probably needs to check the actual argument, i.e. gfc_expr_attr(actual)
with allocatable or pointer attribute - or type being C_PTR (including
C_NULL_PTR).

For the latter:
   expr->ts.type == BT_DERIVED && expr->ts.u.derived
&& expr->ts.u.derived->attr.is_iso_c
&& ??? (some check for ISOCBINDING_PTR)


  parent reply	other threads:[~2011-06-21  9:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 19:51 [Bug fortran/49479] New: " Joost.VandeVondele at pci dot uzh.ch
2011-06-20 20:05 ` [Bug fortran/49479] " Joost.VandeVondele at pci dot uzh.ch
2011-06-20 20:17 ` dominiq at lps dot ens.fr
2011-06-20 21:39 ` burnus at gcc dot gnu.org
2011-06-21  8:59 ` burnus at gcc dot gnu.org
2011-06-21  9:30 ` burnus at gcc dot gnu.org [this message]
2011-06-27 19:02 ` tkoenig at gcc dot gnu.org
2011-06-28 18:59 ` tkoenig at gcc dot gnu.org
2011-07-06 18:51 ` tkoenig at gcc dot gnu.org
2011-07-06 18:52 ` tkoenig at gcc dot gnu.org
2011-09-10 14:46 ` tkoenig at gcc dot gnu.org
2011-09-11  9:37 ` tkoenig 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-49479-4-r1U7ch1BPs@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).