public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@charter.net>
To: Andre Vehreschild <vehre@gmx.de>,
	 GCC-Patches-ML <gcc-patches@gcc.gnu.org>,
	GCC-Fortran-ML <fortran@gcc.gnu.org>
Cc: Dominique Dhumieres <dominiq@lps.ens.fr>
Subject: Re: [Ping, Patch, fortran, pr65548, v1] [5 Regression] gfc_conv_procedure_call
Date: Fri, 03 Apr 2015 00:06:00 -0000	[thread overview]
Message-ID: <551DD96F.2050706@charter.net> (raw)
In-Reply-To: <20150402122830.4153db9b@vepi2>

On 04/02/2015 03:28 AM, Andre Vehreschild wrote:
> Ping!
>
> This should be in 5.1. Dominique and I feel like this patch is nearly obvious.
>
> Regards,
> 	Andre
>
> On Wed, 25 Mar 2015 14:35:54 +0100
> Andre Vehreschild <vehre@gmx.de> wrote:
>
>> Hi all,
>>
>> please find attached a fix for the recently introduced regression when
>> allocating arrays with an intrinsic function for source=. The patch addresses
>> this issue by using gfc_conv_expr_descriptor () for intrinsic functions.
>>
>> Bootstraps and regtests ok on x86_64-linux-gnu/F20.
>>
>> Ok for trunk?

Yes, ok for trunk.

Thanks,

Jerry

  reply	other threads:[~2015-04-03  0:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-65548-26035@http.gcc.gnu.org/bugzilla/>
     [not found] ` <bug-65548-26035-vcFxaNSRns@http.gcc.gnu.org/bugzilla/>
2015-03-25 13:36   ` [Patch, " Andre Vehreschild
2015-04-02 10:28     ` [Ping, Patch, " Andre Vehreschild
2015-04-03  0:06       ` Jerry DeLisle [this message]
2015-04-07 14:12         ` Andre Vehreschild
2015-04-29 12:52           ` [Patch, fortran, pr65548, 2nd take] [5/6 " Andre Vehreschild
2015-04-30 13:30             ` [Patch, fortran, pr65548, 2nd take, v3] " Andre Vehreschild
2015-05-12 22:04               ` Mikael Morin
2015-05-13  9:31                 ` Andre Vehreschild
2015-05-14  9:49                   ` [Patch, fortran, pr65548, 2nd take, v4] " Andre Vehreschild
2015-05-19  8:52                     ` [Patch, fortran, pr65548, 2nd take, v5] " Andre Vehreschild
2015-05-19 14:07                       ` Mikael Morin
2015-05-20  8:31                         ` Andre Vehreschild
2015-05-20 13:29                           ` Mikael Morin
2015-05-20 15:28                             ` Andre Vehreschild
2015-05-26 17:34                               ` [Patch, fortran, pr65548, addendum] " Andre Vehreschild
2015-05-27  8:28                                 ` Thomas Koenig
2015-05-27 10:12                                   ` Andre Vehreschild

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=551DD96F.2050706@charter.net \
    --to=jvdelisle@charter.net \
    --cc=dominiq@lps.ens.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=vehre@gmx.de \
    /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).