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/67431] ALLOCATE with SOURCE ignores overloaded assignment operator and uses intrinsic when copying values
Date: Fri, 04 Sep 2015 09:09:00 -0000	[thread overview]
Message-ID: <bug-67431-4-ZX7Jcorxg5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67431-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
>From Damian Rouson:

NAG 6.0 ouptput:

SIZE(A) 4 A 765 765 765 765


Cray Compiler Environment (CCE) 8.3.14 output:

SIZE(A) 4 A 4*765


Portland Group 15.7-0 output:

SIZE(A)            4 A          765          765          765          765

and Andre Vehreschild told me on IRC that gfortran agrees with ifort.


  parent reply	other threads:[~2015-09-04  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02  5:49 [Bug fortran/67431] New: " alipasha.celeris at gmail dot com
2015-09-02  8:45 ` [Bug fortran/67431] " dominiq at lps dot ens.fr
2015-09-04  9:09 ` dominiq at lps dot ens.fr [this message]
2015-09-29 17:15 ` dominiq at lps dot ens.fr

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-67431-4-ZX7Jcorxg5@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).