public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Janne Blomqvist <blomqvist.janne@gmail.com>
Cc: Damian Rouson <damian@sourceryinstitute.org>,
	GNU GFortran <fortran@gcc.gnu.org>,
		Jerry DeLisle <jvdelisle@gcc.gnu.org>
Subject: Re: Development stage timeline?
Date: Wed, 28 Oct 2015 19:41:00 -0000	[thread overview]
Message-ID: <CAGkQGi+F=-jzwOscCw3nmy3EU82oSggQP9C-OkKRMjqjsjWxHQ@mail.gmail.com> (raw)
In-Reply-To: <CAO9iq9ELNsq_jgh_aG3ZZqSnjQepFEWxnDcB+f4dK4ibCfpPLQ@mail.gmail.com>

Dear Damian and Janne,

I have beaten my head against various approaches to parameterized
derived types and have come up against the proverbial brick-wall. I
can see how to do it now, having tried so many blind alleys. Whether
or not I can come up with something before the end of stage-1, I don't
know. By way of light relief, I have been clearing my backlog of PRs
:-)

The trick with pdts is going to be to turn them into a set of macros,
that substitute the kind parameters and produce appropriate
initialization procedures, using the len parameters, and finalization
routines. I have been researching various ways of doing this,
including m4, but have concluded that rolling my own is the best way
to proceed.

As Janne says, we are not so tightly bound by the deadlines as C and
C++ and so there is a little bit of leeway.....

I wonder if Jerry has made any progress with derived type IO?

Cheers

Paul

On 28 October 2015 at 18:15, Janne Blomqvist <blomqvist.janne@gmail.com> wrote:
> On Wed, Oct 28, 2015 at 7:08 PM, Damian Rouson
> <damian@sourceryinstitute.org> wrote:
>> All,
>>
>> Could anyone provide an estimate of when GCC development will move to the next stage of development?  I assume that date is the deadline for submitting patches that support new features.
>
> You can find the latest status report here:
> https://gcc.gnu.org/ml/gcc/2015-10/msg00113.html
>
> (In principle, AFAIU, Fortran isn't bound by this as tightly as the C
> and C++ frontends, so the Fortran maintainers have some leeway to
> accept patches at their discretion. That being said, the schedule is
> there for a good reason, so it might make sense to follow it
> nonetheless.)
>
>
> --
> Janne Blomqvist



-- 
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-10-28 19:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 17:08 Damian Rouson
2015-10-28 17:15 ` Janne Blomqvist
2015-10-28 19:41   ` Paul Richard Thomas [this message]
2015-10-29 17:45     ` Jerry DeLisle
2015-10-29 20:03       ` Damian Rouson
2015-10-29 20:04     ` Damian Rouson
2015-10-29 19:59   ` Damian Rouson

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='CAGkQGi+F=-jzwOscCw3nmy3EU82oSggQP9C-OkKRMjqjsjWxHQ@mail.gmail.com' \
    --to=paul.richard.thomas@gmail.com \
    --cc=blomqvist.janne@gmail.com \
    --cc=damian@sourceryinstitute.org \
    --cc=fortran@gcc.gnu.org \
    --cc=jvdelisle@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).