From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: explain representation of Fortran array types
Date: Wed, 25 Aug 2004 15:42:00 -0000 [thread overview]
Message-ID: <vt2acwjfcn4.fsf@zenia.home> (raw)
2004-08-25 Jim Blandy <jimb@redhat.com>
* gdbtypes.h (TYPE_CODE_ARRAY): Doc fix.
*** 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 15:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vt2acwjfcn4.fsf@zenia.home \
--to=jimb@redhat.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