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/52022] [4.5/4.6/4.7 Regression] Wrong-code with procedures passed as actual argument
Date: Sat, 28 Jan 2012 11:00:00 -0000	[thread overview]
Message-ID: <bug-52022-4-meTuc6aoOn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52022-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-28 10:00:20 UTC ---
Author: burnus
Date: Sat Jan 28 10:00:13 2012
New Revision: 183665

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183665
Log:
2012-01-28  Tobias Burnus  <burnus@net-b.de>

        PR fortran/52022
        * trans-expr.c (gfc_conv_procedure_call): Fix passing
        of functions, which return allocatables.

2012-01-28  Tobias Burnus  <burnus@net-b.de>

        PR fortran/52022
        * gfortran.dg/dummy_procedure_7.f90: New.


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


  parent reply	other threads:[~2012-01-28 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 17:54 [Bug fortran/52022] New: " burnus at gcc dot gnu.org
2012-01-27 18:05 ` [Bug fortran/52022] " burnus at gcc dot gnu.org
2012-01-27 20:43 ` burnus at gcc dot gnu.org
2012-01-27 21:07 ` jakub at gcc dot gnu.org
2012-01-28 11:00 ` burnus at gcc dot gnu.org [this message]
2012-01-28 11:41 ` burnus at gcc dot gnu.org
2012-01-28 11:55 ` burnus 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-52022-4-meTuc6aoOn@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).