public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54070] Wrong code with allocatable deferred-length (array) function results
Date: Tue, 24 Jul 2012 14:40:00 -0000	[thread overview]
Message-ID: <bug-54070-4-xP1sw7xWpW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54070-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54070

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-07-24 14:39:54 UTC ---
Dominique mentions that the failure of the array test case seems to be a
regression between Rev. 188654 and 188694. Well, there was only one commit
during that time (Rev. 188692, 2012-06-16): The one for PR 53642 / PR45170:
"Ensure that the RHS string length is evaluated before the deferred-length LHS
is reallocated."

Using my (older) build of Rev. 187316 (2012-05-09), the array test case fails
with the same error as today, but the scalar example of comment 0 works. (The
dump looks fine and identical to today's trunk plus patch of comment 2.)

Thus, the scalar version got broken between 187316 and 188654; the array
version got repaired after 187316 and got broken again before 188694 (i.e. with
188692).


  parent reply	other threads:[~2012-07-24 14:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23  9:33 [Bug fortran/54070] New: " burnus at gcc dot gnu.org
2012-07-23 10:23 ` [Bug fortran/54070] " burnus at gcc dot gnu.org
2012-07-24  9:28 ` burnus at gcc dot gnu.org
2012-07-24 14:40 ` burnus at gcc dot gnu.org [this message]
2013-07-15  6:26 ` zeccav at gmail dot com
2014-01-07 11:15 ` dominiq at lps dot ens.fr
2014-03-23  0:26 ` [Bug fortran/54070] [4.8/4.9 Regression] " dominiq at lps dot ens.fr
2014-03-24  5:29 ` rouson at stanford dot edu
2014-03-31  8:56 ` rguenth at gcc dot gnu.org
2014-03-31  9:09 ` rguenth at gcc dot gnu.org
2014-05-22  9:05 ` [Bug fortran/54070] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-11-16 15:31 ` [Bug fortran/54070] [4.8/4.9/5 " dominiq at lps dot ens.fr
2014-11-16 15:33 ` dominiq at lps dot ens.fr
2014-12-08 23:22 ` dominiq at lps dot ens.fr
2014-12-19 13:26 ` jakub at gcc dot gnu.org
2015-03-10 17:58 ` dominiq at lps dot ens.fr
2015-06-23  8:19 ` [Bug fortran/54070] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 19:54 ` [Bug fortran/54070] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:27 ` jakub at gcc dot gnu.org
2015-08-31 16:45 ` zeccav at gmail dot com
2015-09-03 21:16 ` 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-54070-4-xP1sw7xWpW@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).