public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikael Morin <mikael.morin@sfr.fr>
To: Andre Vehreschild <vehre@gmx.de>
Cc: GCC-Fortran-ML <fortran@gcc.gnu.org>,
	GCC-Patches-ML	<gcc-patches@gcc.gnu.org>,
	Antony Lewis <antony@cosmologist.info>
Subject: Re: [Patch 1/2, Fortran, pr60322]  [OOP] Incorrect bounds on polymorphic dummy array
Date: Mon, 23 Mar 2015 19:28:00 -0000	[thread overview]
Message-ID: <5510694E.2010201@sfr.fr> (raw)
In-Reply-To: <20150323164943.76daeabe@vepi2>

Le 23/03/2015 16:49, Andre Vehreschild a écrit :
> I see your point. Currently I am bootstraping and regtesting some patches for
> commit. While this is running, my machine is nearly unusable. I will look into
> this as soon, as my machine allows, but probably not before tomorrow.
> 
There is no hurry, the patch(es) will probably have to wait for next
stage 1.

  reply	other threads:[~2015-03-23 19:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 17:19 Andre Vehreschild
2015-03-23 12:29 ` Mikael Morin
2015-03-23 12:44   ` Andre Vehreschild
2015-03-23 14:58     ` Mikael Morin
2015-03-23 15:49       ` Andre Vehreschild
2015-03-23 19:28         ` Mikael Morin [this message]
2015-03-24 10:13     ` Paul Richard Thomas
2015-03-24 17:06       ` [Patch, Fortran, pr60322] was: " Andre Vehreschild
2015-03-25  9:43         ` Dominique d'Humières
2015-03-25 16:57           ` Andre Vehreschild
2015-03-26  9:27             ` Dominique d'Humières
2015-03-27 12:48         ` Paul Richard Thomas
2015-04-05  9:13           ` Paul Richard Thomas
2015-04-09 12:37             ` Andre Vehreschild
2015-04-14 17:01               ` [Patch, Fortran, pr60322, addendum] " Andre Vehreschild
2015-04-16 19:13                 ` Paul Richard Thomas
2015-04-23 11:34                   ` [commited, Patch, " Andre Vehreschild
2015-04-27 17:43                     ` 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=5510694E.2010201@sfr.fr \
    --to=mikael.morin@sfr.fr \
    --cc=antony@cosmologist.info \
    --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).