Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@streamline-computing.com>
To: Jim Blandy <jimb@redhat.com>
Cc: patches <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH/RFA] PR gdb/648  (eval.c approval reqd)
Date: Wed, 25 Aug 2004 07:24:00 -0000	[thread overview]
Message-ID: <1093419688.18611.48.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com> (raw)
In-Reply-To: <vt2acwjkbmf.fsf@zenia.home>

Hi Jim, 

Yes, that's correct.  

Cheers
David

On Wed, 2004-08-25 at 06:52, Jim Blandy wrote:
> So, I'm just trying to get my head around what's going on here.  Would
> you say the following comment change would be correct?
> 
> *** gdbtypes.h.~1.58.~	2004-08-09 17:42:14.000000000 -0500
> --- gdbtypes.h	2004-08-25 00:51:03.000000000 -0500
> *************** enum type_code
> *** 82,88 ****
>     {
>       TYPE_CODE_UNDEF,		/* Not used; catches errors */
>       TYPE_CODE_PTR,		/* Pointer type */
> !     TYPE_CODE_ARRAY,		/* Array type with lower & upper bounds. */
>       TYPE_CODE_STRUCT,		/* C struct or Pascal record */
>       TYPE_CODE_UNION,		/* C union or Pascal variant part */
>       TYPE_CODE_ENUM,		/* Enumeration type */
> --- 82,108 ----
>     {
>       TYPE_CODE_UNDEF,		/* Not used; catches errors */
>       TYPE_CODE_PTR,		/* Pointer type */
> ! 
> !     /* Array type with lower & upper bounds.
> ! 
> !        Regardless of the language, GDB represents multidimensional
> !        array types the way C does: as arrays of arrays.  So an
> !        instance of a GDB array type T can always be seen as a series
> !        of instances of TYPE_TARGET_TYPE (T) laid out sequentially in
> !        memory.
> ! 
> !        Row-major languages like C lay out multi-dimensional arrays so
> !        that incrementing the rightmost index in a subscripting
> !        expression results in the smallest change in the address of the
> !        element referred to.  Column-major languages like Fortran lay
> !        them out so that incrementing the leftmost index results in the
> !        smallest change.
> ! 
> !        This means that, in column-major languages, working our way
> !        from type to target type corresponds to working through indices
> !        from right to left, not left to right.  */
> !     TYPE_CODE_ARRAY,
> ! 
>       TYPE_CODE_STRUCT,		/* C struct or Pascal record */
>       TYPE_CODE_UNION,		/* C union or Pascal variant part */
>       TYPE_CODE_ENUM,		/* Enumeration type */


  reply	other threads:[~2004-08-25  7:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-06 22:10 [PATCH/RFA] PR gdb/648 David Lecomber
2004-08-13 10:25 ` David Lecomber
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 [this message]
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=1093419688.18611.48.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com \
    --to=david@streamline-computing.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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