From: Tobias Burnus <burnus@net-b.de>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gcc patches <gcc-patches@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran] Support scalar coarrays in this_image/ucobound/image_index
Date: Fri, 06 May 2011 23:02:00 -0000 [thread overview]
Message-ID: <4DC47E0C.4080203@net-b.de> (raw)
In-Reply-To: <BANLkTi=4vt9wkpbngZ1e_ExWp50k4Wtauw@mail.gmail.com>
Am 07.05.2011 00:50, schrieb H.J. Lu:
> On Wed, May 4, 2011 at 11:07 PM, Tobias Burnus<burnus@net-b.de> wrote:
>> Is the patch OK for the trunk?
> This caused: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=4891
That happens if patches do not get approved in the order in which they
were written/submitted.
The failure is fixed by my patch at:
http://gcc.gnu.org/ml/fortran/2011-05/msg00023.html
(The patch did not include a test case (I didn't include the one I had)
- but seemingly we now have one, which already in the trunk.)
Tobias
prev parent reply other threads:[~2011-05-06 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 6:51 Tobias Burnus
2011-05-06 16:56 ` Daniel Kraft
2011-05-06 23:02 ` H.J. Lu
2011-05-06 23:02 ` Tobias Burnus [this message]
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=4DC47E0C.4080203@net-b.de \
--to=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
/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).