This is the mail archive of the
mailing list for the GCC project.
Re: [Patch, fortran] First steps to array descriptor reform
- From: Thomas Koenig <tkoenig at netcologne dot de>
- To: Paul Richard Thomas <paul dot richard dot thomas at gmail dot com>
- Cc: fortran at gcc dot gnu dot org, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Sun, 07 Jun 2009 20:47:28 +0200
- Subject: Re: [Patch, fortran] First steps to array descriptor reform
- References: <firstname.lastname@example.org>
On Sun, 2009-06-07 at 19:42 +0200, Paul Richard Thomas wrote:
> The order of play that I see is:
> (i) Apply the attached patch;
> (ii) Modify the descriptor in the frontend and the library.
> (iii) Ensure that there is no runtime performance loss and submit at
> this stage so that the API change occurs as early as possible; and
> (iv) FIx all the associated PRs.
Makes sense to me, this way, with one open point...
> The attached bootstraps and regtests on FC9/x86_64 - OK for trunk?
So far, the array descriptor macro patches are implemented on
fortran-dev, so it would make sense to either
a) do your steps (i) to (iv) on fortran-dev, then move the whole thing
to trunk, or
b) merge fortran-dev to trunk completely before step (ii).