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/61138] [4.8/4.9/5 Regression] Wrong code with pointer-bounds remapping
Date: Sat, 21 Mar 2015 18:16:00 -0000	[thread overview]
Message-ID: <bug-61138-4-V6ybToQhmJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61138-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Mikael Morin <mikael at gcc dot gnu.org> ---
Author: mikael
Date: Sat Mar 21 15:45:13 2015
New Revision: 221556

URL: https://gcc.gnu.org/viewcvs?rev=221556&root=gcc&view=rev
Log:
    Backport from trunk:
    2015-03-14  Mikael Morin  <mikael@gcc.gnu.org>

    PR fortran/61138
fortran/
    * trans-expr.c (gfc_trans_pointer_assignment): Clear DESCRIPTOR_ONLY
    field before reusing LSE.
testsuite/
    * gfortran.dg/pointer_remapping_9.f90: New.


Added:
    branches/gcc-4_8-branch/gcc/testsuite/gfortran.dg/pointer_remapping_9.f90
Modified:
    branches/gcc-4_8-branch/gcc/fortran/ChangeLog
    branches/gcc-4_8-branch/gcc/fortran/trans-expr.c
    branches/gcc-4_8-branch/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2015-03-21 15:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-10  8:30 [Bug fortran/61138] New: " burnus at gcc dot gnu.org
2014-05-10  9:13 ` [Bug fortran/61138] [4.8/4.9/4.10 Regression] " dominiq at lps dot ens.fr
2014-05-13  9:55 ` rguenth at gcc dot gnu.org
2014-05-22  9:06 ` rguenth at gcc dot gnu.org
2014-05-25 12:28 ` mikael at gcc dot gnu.org
2014-12-19 13:34 ` [Bug fortran/61138] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-02-06 21:00 ` mikael at gcc dot gnu.org
2015-02-09 12:57 ` mikael at gcc dot gnu.org
2015-03-14 12:24 ` mikael at gcc dot gnu.org
2015-03-21 15:47 ` mikael at gcc dot gnu.org
2015-03-21 18:16 ` mikael at gcc dot gnu.org [this message]
2015-03-21 18:20 ` 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-61138-4-V6ybToQhmJ@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).