public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: "Dominique d'Humières" <dominiq@lps.ens.fr>
Cc: gfortran@gcc.gnu.org, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] [6 Regression] ICE: in gfc_get_descriptor_dimension, at fortran/trans-array.c:268
Date: Tue, 22 Dec 2015 17:34:00 -0000	[thread overview]
Message-ID: <CAGkQGiKpH6GP+YMVahNVFykcBStY5t5OrRgNn19t3uRcFUvv3A@mail.gmail.com> (raw)
In-Reply-To: <CEAE3FE2-16DC-4FC3-847D-23022D5569E1@lps.ens.fr>

Dear Dominique,

This will have to wait until after the 28th. For reasons that I cannot
determine, I don't seem able to tunnel through to gnu central. Given
the imminent arrival of guests for the holiday, I do not feel
motivated to investigate further :-)

Happy holidays to one and all!

Paul

On 20 December 2015 at 13:39, Dominique d'Humières <dominiq@lps.ens.fr> wrote:
> Dear Paul,
>> This is a rather trivial patch... going on 'obvious' in fact. However,
>> I must confess to not being entirely sure why the problem is
>> occurring. Deferred arrays are emanating from the finalizer that are
>> being presented as ARRAY_TYPES rather than descriptors. What ever is
>> the reason, the fix is both safe and does what is required.
> The patch works as advertised. However the test should be either compile only, or "dejagnufied".
>
> Cheers,
>
> Dominique
>



-- 
Outside of a dog, a book is a man's best friend. Inside of a dog it's
too dark to read.

Groucho Marx

  reply	other threads:[~2015-12-22 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20 12:39 Dominique d'Humières
2015-12-22 17:34 ` Paul Richard Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-18 11:31 Paul Richard Thomas

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=CAGkQGiKpH6GP+YMVahNVFykcBStY5t5OrRgNn19t3uRcFUvv3A@mail.gmail.com \
    --to=paul.richard.thomas@gmail.com \
    --cc=dominiq@lps.ens.fr \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gfortran@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).