public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66927] [6.0 regression] ICE in gfc_conf_procedure_call
Date: Sat, 18 Jul 2015 10:01:00 -0000	[thread overview]
Message-ID: <bug-66927-4-mjnmsZI9ZK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66927-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Actually, we are using now

allocate (obj(1:size (func ()))
obj = func ()

as you are saying 
allocate (obj, source = func ())
had problems in gfortran 4.7.X. 
So the issue is not a problem for our code(s). 

But you are saying that the code triggering the ICE violates the Fortran
standard?
>From gcc-bugs-return-492731-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 18 10:15:32 2015
Return-Path: <gcc-bugs-return-492731-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72443 invoked by alias); 18 Jul 2015 10:15:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72397 invoked by uid 48); 18 Jul 2015 10:15:28 -0000
From: "vehre at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66927] [6.0 regression] ICE in gfc_conf_procedure_call
Date: Sat, 18 Jul 2015 10:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vehre at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-66927-4-u4plBNf9U4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66927-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66927-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-07/txt/msg01621.txt.bz2
Content-length: 795

https://gcc.gnu.org/bugzilla/show_bug.cgi?idf927

vehre at gcc dot gnu.org changed:

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

--- Comment #5 from vehre at gcc dot gnu.org ---
I am not that bold anymore to interpret the nasty standard. I wanted to
express, that the allocate(obj, source=func()) is now sufficient.

I made some bad experience trying to interpret the standard and was told off
not to do so. Therefore, I will not say "yes, it violates the standard" nor
"no, it doesn't".

Given there are many programs, that use the work-around you've shown, I am
unsure what to do here. But you are right, ICE'ing is a no go.


  parent reply	other threads:[~2015-07-18 10:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-18  9:40 [Bug fortran/66927] New: " juergen.reuter at desy dot de
2015-07-18  9:41 ` [Bug fortran/66927] " juergen.reuter at desy dot de
2015-07-18  9:55 ` dominiq at lps dot ens.fr
2015-07-18  9:58 ` vehre at gcc dot gnu.org
2015-07-18 10:01 ` juergen.reuter at desy dot de [this message]
2015-07-18 13:01 ` vehre at gcc dot gnu.org
2015-07-21  7:58 ` [Bug fortran/66927] [6 Regression] " rguenth at gcc dot gnu.org
2015-08-06 10:09 ` vehre at gcc dot gnu.org
2015-10-06  8:40 ` vehre at gcc dot gnu.org
2015-10-16  8:34 ` rguenth at gcc dot gnu.org
2015-10-25 12:29 ` vehre at gcc dot gnu.org
2015-10-25 13:03 ` vehre at gcc dot gnu.org
2015-10-25 16:47 ` hjl.tools at gmail dot com
2015-10-25 18:04 ` vehre at gcc dot gnu.org
2015-10-26 13:04 ` vehre at gcc dot gnu.org
2015-10-26 22:43 ` juergen.reuter at desy dot de
2015-10-26 23:42 ` juergen.reuter at desy dot de
2015-10-27  0:55 ` kargl at gcc dot gnu.org
2015-10-27  1:01 ` juergen.reuter at desy dot de

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-66927-4-mjnmsZI9ZK@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).