Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@streamline-computing.com>
To: patches <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH/RFA] PR gdb/648
Date: Fri, 13 Aug 2004 10:25:00 -0000	[thread overview]
Message-ID: <1092393966.22361.19.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com> (raw)
In-Reply-To: <1091830216.4188.23.camel@localhost>

Hi,

Is anyone looking into this -- I can't commit without a go-ahead!  

Cheers
David

On Fri, 2004-08-06 at 23:10, David Lecomber wrote:
> This is a fix for a long-standing bug with multi-dimensional arrays in
> fortran.  When printing individual elements of an array,
> evaluate_subexp_standard understood the dimensions of the array to be in
> the opposite order to that of the whatis or entire array printing.  This
> led to bug 648, which was present for G77 compiled code, but the problem
> was reversed for commercial compilers such as Intel or Portland.
> 
> G77 puts things in row-major order, as far as I can ascertain all other
> fortran compilers do column major.  This is handled in the dwarf2read
> change, and now column major array types are reversed during the reading
> to fit with GDB's struct type.
> 
> 2004-08-06  David Lecomber  <dsl@sources.redhat.com>
>  
>         Fix PR gdb/648
>         * dwarf2read.c (read_array_type): Handle column major arrays
>         correctly.  Assume column major for Fortran except with G77
>         compiler.
>         * eval.c (evaluate_subexp_standard): Assume Fortran arrays are
>         oriented large to small in type structure.
> 
> 
> Attached is a test program and test script, should return true for all 
> comparisons..  
> 
> I'm sure there'll be some comments, so please feel free to suggest some
> reformatting!
> 
> David.
> 


  reply	other threads:[~2004-08-13 10:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-06 22:10 David Lecomber
2004-08-13 10:25 ` David Lecomber [this message]
2004-08-13 10:32   ` Michael Chastain
2004-08-13 22:14 ` Jim Blandy
2004-08-16 12:33   ` David Lecomber
2004-08-16 12:38   ` David Lecomber
2004-08-18 16:36     ` Jim Blandy
2004-08-20 13:37       ` [PATCH/RFA] PR gdb/648 (eval.c approval reqd) David Lecomber
2004-08-20 13:45         ` David Lecomber
2004-08-25  5:53         ` Jim Blandy
2004-08-25  7:24           ` David Lecomber
2004-08-27  0:00         ` Jim Blandy
2004-08-27  9:15           ` David Lecomber
2004-08-27 13:52             ` Andrew Cagney
2004-08-27 13:58               ` Michael Chastain
2004-08-27 14:14                 ` Andrew Cagney
2004-08-27 14:57                   ` Michael Chastain
2004-08-27 15:57                     ` Andrew Cagney
2004-08-27 16:15                       ` Michael Chastain
2004-08-30 14:17                         ` Andrew Cagney
2004-08-23 19:26       ` [PATCH/RFA] PR gdb/648 Andrew Cagney
2004-08-24 18:03         ` Jim Blandy
2004-08-15  8:19 ` Michael Chastain

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=1092393966.22361.19.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com \
    --to=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