public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65585] Implicit allocation of unallocated array with an implicit summation
Date: Thu, 26 Mar 2015 16:42:00 -0000	[thread overview]
Message-ID: <bug-65585-4-csE39N7kep@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65585-4@http.gcc.gnu.org/bugzilla/>

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
gfortran is behaving as expected: iamwild is allocated on assignment as stated
in the manual

-frealloc-lhs
An allocatable left-hand side of an intrinsic assignment is automatically
(re)allocated if it is either unallocated or has a different shape. The option
is enabled by default except when -std=f95 is given. See also -Wrealloc-lhs. 

Note this apply to full arrays only, hence the segfault if you use iamwild(:)
and iamwild unallocated.

> PS: took me the day to understand why my code was not working with another
> compiler... :-/

If the "other compiler" is ifort, this behavior is not the default and has to
be set by some option.


  reply	other threads:[~2015-03-26 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 16:26 [Bug fortran/65585] New: " dirteat at gmail dot com
2015-03-26 16:42 ` dominiq at lps dot ens.fr [this message]
2015-03-26 16:59 ` [Bug fortran/65585] " dirteat at gmail dot com
2015-03-26 17:17 ` mikael 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-65585-4-csE39N7kep@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).