public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64980] [5 Regression] ICE in trans-expr.c
Date: Sat, 14 Feb 2015 12:28:00 -0000	[thread overview]
Message-ID: <bug-64980-4-l6PSOq5Gxy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64980-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Mikael Morin <mikael at gcc dot gnu.org> ---
Created attachment 34755
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34755&action=edit
Another proposed  fix

(In reply to Bernd Edlinger from comment #10)
> Yes, but I have no idea how to know how the result is going to be
> used, in gfc_conv_procedure_call, line 4544.  If you have an idea
> how to detect this case, that would be great.

It is used as argument to the procedure, and also added to the interface
mapping mechanism through gfc_add_interface_mapping.
>From there, it is dropped if the resulting size can be determined by other
means; otherwised it is used to set the array result bounds.

The attached patch (untested so far) makes a copy of the reference before
passing it through VIEW_CONVERT_EXPR.
It avoids the second V_C_E at least.

> 
> Until yesterday, I thought the result is always used in a procedure call
> context, and I thought we only have aliasing violations on different
> variations of the same principal class, but that was also wrong.
What I don't understand is why there isn't something alike needed for non-class
arrays?  They also use different variations of the same principal class, don't
they?


  parent reply	other threads:[~2015-02-14 12:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-64980-4@http.gcc.gnu.org/bugzilla/>
2015-02-09 12:14 ` [Bug fortran/64980] [5.0 " janus at gcc dot gnu.org
2015-02-09 12:25 ` janus at gcc dot gnu.org
2015-02-09 13:05 ` dominiq at lps dot ens.fr
2015-02-09 13:45 ` mikael at gcc dot gnu.org
2015-02-09 14:35 ` [Bug fortran/64980] [5 " rguenth at gcc dot gnu.org
2015-02-09 15:57 ` mikael at gcc dot gnu.org
2015-02-12 21:20 ` bernd.edlinger at hotmail dot de
2015-02-13 11:22 ` dominiq at lps dot ens.fr
2015-02-13 19:01 ` bernd.edlinger at hotmail dot de
2015-02-13 20:03 ` mikael at gcc dot gnu.org
2015-02-13 21:10 ` bernd.edlinger at hotmail dot de
2015-02-14 12:28 ` mikael at gcc dot gnu.org [this message]
2015-02-14 15:08 ` dominiq at lps dot ens.fr
2015-02-14 17:45 ` mikael at gcc dot gnu.org
2015-02-14 17:49 ` mikael at gcc dot gnu.org
2015-02-14 21:30 ` bernd.edlinger at hotmail dot de
2015-02-15 12:30 ` bernd.edlinger at hotmail dot de
2015-02-16  7:32 ` dominiq at lps dot ens.fr
2015-02-16  7:54 ` bernd.edlinger at hotmail dot de
2015-02-16 13:55 ` dominiq at lps dot ens.fr
2015-02-16 19:44 ` bernd.edlinger at hotmail dot de
2015-02-22 19:45 ` edlinger at gcc dot gnu.org
2015-02-23 13:37 ` edlinger 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-64980-4-l6PSOq5Gxy@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).