From: Daniel Jacobowitz <drow@mvista.com>
To: David Lecomber <david@streamline-computing.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Large array fix for Fortran.
Date: Fri, 16 May 2003 15:32:00 -0000 [thread overview]
Message-ID: <20030516153246.GB5866@nevyn.them.org> (raw)
In-Reply-To: <20030516122426.B31934@streamline-computing.com>
On Fri, May 16, 2003 at 12:24:26PM +0100, David Lecomber wrote:
> Resubmitted as I now have copyright assignment..
>
> This patch limits the number of elements printed from a
> multidimensional array to the correct number of elements, rather than
> the number of top level elements (eg. rows). Very useful for most
> Fortran programmers, as they have a tendency to have obscenely large
> multi-d arrays and without this fix info locals, info args and others
> tend to be kinda slow..
>
> A similar fix for C wouldn't go amiss, but is less urgent..
>
> David
Some comments:
- Missing ChangeLog.
- You introduced a whitespace change on the before the body of
f77_print_array_1; please try to avoid mixing whitespace changes
with bug fixes. Whitespace in your changes is a little bit off,
too, for instance the two spaces before the &&:
> ! for (i = 0; i < F77_DIM_SIZE (nss) && *elts < print_max; i++)
and the space before the comma:
> ! for (i = 0; (i < F77_DIM_SIZE (nss) && (*elts) < print_max); i++ , (*elts)++)
It may be trivial, but consistency in this sort of thing makes the
code much easier to read.
Otherwise, this patch is OK. I'd appreciate it if you could repost it
with ChangeLog and formatting fixes, though.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-05-16 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 21:32 Patches to improve Fortran support David Lecomber
2003-05-16 11:24 ` [PATCH] Improvements to " David Lecomber
2003-05-16 15:25 ` Daniel Jacobowitz
2003-05-16 16:08 ` David Carlton
2003-05-16 11:25 ` [PATCH] Large array fix for Fortran David Lecomber
2003-05-16 15:32 ` Daniel Jacobowitz [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=20030516153246.GB5866@nevyn.them.org \
--to=drow@mvista.com \
--cc=david@streamline-computing.com \
--cc=gdb-patches@sources.redhat.com \
/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