From: Joel Brobecker <brobecker@adacore.com>
To: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>
Cc: Keven Boell <keven.boell@linux.intel.com>,
gdb-patches@sourceware.org, sanimir.agovic@intel.com,
Keven Boell <keven.boell@intel.com>
Subject: Re: PING: [V3 00/21] Fortran dynamic array support
Date: Wed, 04 Feb 2015 14:18:00 -0000 [thread overview]
Message-ID: <20150204141753.GB4738@adacore.com> (raw)
In-Reply-To: <20150204132224.GA31304@physik.fu-berlin.de>
> As I saw, Keven has split them into parts in mid January:
> https://sourceware.org/ml/gdb-patches/2015-01/threads.html#00376
>
> Any estimate when you have time to start reviewing them piecewise?
> Or other comments?
>
> I think it would be great if 7.10 (8.0?) would support Fortran 90
> code out of the box.
Yes, sorry, I meant to send an update last weekend about it,
to say that I would look at them soon, and I was so busy that
I forgot. There was still a bit of a misunderstanding over how
the patches should be split (IMO), but I will simply take the
first patch, which is IIRC the nerve of the series, and start with
that, and explain precisely how some of the other pieces should
be merged into that.
Expect me to look into them this coming weekend. The reason for
the delays is that I have to think over an issue I mentioned
previously, which is the fact that we can't augment the size
of struct type * for _all_ types when only a handful really
need them. We need to find a way to limit that increase, because
"struct type" is one of the types where the size of the struct
is extremely sensitive.
--
Joel
prev parent reply other threads:[~2015-02-04 14:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 9:22 Keven Boell
2014-09-10 9:22 ` [V3 10/21] vla: add NEWS entry for " Keven Boell
2014-09-10 17:03 ` Eli Zaretskii
2014-09-10 9:22 ` [V3 12/21] test: evaluate dynamic arrays using Fortran primitives Keven Boell
2014-09-10 9:22 ` [V3 17/21] test: accessing dynamic array history values Keven Boell
2014-09-10 9:22 ` [V3 06/21] vla: get dynamic array corner cases to work Keven Boell
2014-09-10 9:22 ` [V3 20/21] test: test sizeof for dynamic fortran arrays Keven Boell
2014-09-10 9:22 ` [V3 07/21] vla: changed string length semantic Keven Boell
2014-09-10 9:22 ` [V3 19/21] test: basic MI test for the dynamic array support Keven Boell
2014-09-10 9:22 ` [V3 08/21] vla: get Fortran dynamic strings working Keven Boell
2014-09-10 9:22 ` [V3 16/21] test: dynamic arrays passed to functions Keven Boell
2014-09-10 9:22 ` [V3 11/21] test: basic tests for dynamic array evaluations in Fortran Keven Boell
2014-09-10 9:22 ` [V3 04/21] vla: reconstruct value to compute bounds of target type Keven Boell
2014-09-10 9:22 ` [V3 05/21] vla: use value constructor instead of raw-buffer manipulation Keven Boell
2014-09-10 9:22 ` [V3 02/21] vla: make dynamic fortran arrays functional Keven Boell
2014-09-10 9:22 ` [V3 18/21] test: dynamic string evaluations Keven Boell
2014-09-10 9:22 ` [V3 09/21] vla: add stride support to fortran arrays Keven Boell
2014-09-10 9:22 ` [V3 14/21] test: correct ptype of dynamic arrays in Fortran Keven Boell
2014-09-10 9:22 ` [V3 01/21] vla: introduce allocated/associated flags Keven Boell
2014-09-10 9:22 ` [V3 13/21] test: dynamic arrays passed to subroutines Keven Boell
2014-09-10 9:22 ` [V3 03/21] vla: make field selection work with vla Keven Boell
2014-09-10 9:22 ` [V3 15/21] test: evaluating allocation/association status Keven Boell
2014-09-10 9:22 ` [V3 21/21] test: stride support for dynamic arrays Keven Boell
2014-10-02 8:35 ` PING: [V3 00/21] Fortran dynamic array support Tobias Burnus
2014-10-02 15:00 ` Joel Brobecker
2014-11-17 8:59 ` Tobias Burnus
2014-11-17 10:05 ` Joel Brobecker
2014-12-09 8:00 ` Tobias Burnus
2014-12-09 9:18 ` Joel Brobecker
2014-12-09 10:03 ` Keven Boell
2015-02-04 13:22 ` Tobias Burnus
2015-02-04 14:18 ` Joel Brobecker [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=20150204141753.GB4738@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=keven.boell@intel.com \
--cc=keven.boell@linux.intel.com \
--cc=sanimir.agovic@intel.com \
--cc=tobias.burnus@physik.fu-berlin.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).