Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: Start Fortran support for variable objects.
Date: Thu, 30 Jun 2005 13:15:00 -0000	[thread overview]
Message-ID: <20050630131454.GA8241@nevyn.them.org> (raw)
In-Reply-To: <17091.46378.720749.411474@farnswood.snap.net.nz>

On Thu, Jun 30, 2005 at 09:02:34PM +1200, Nick Roberts wrote:
> Daniel Jacobowitz writes:
>  > On Thu, Jun 30, 2005 at 09:29:16AM +1200, Nick Roberts wrote:
>  > > 
>  > > This patch adjusts the offset from 0 to 1 to allow the display of arrays
>  > > in Fortran using variable objects.
>  > 
>  > I see that you're hardcoding this based on language.  Can we do it
>  > based on type instead?  Specifically, TYPE_LOW_BOUND and
>  > TYPE_HIGH_BOUND.  We have got type information here - unless I'm
>  > misreading, var->type should be the type of the array.
> 
> They look pretty similar to me.
> 
> C:
> 
> (top-gdb) p TYPE_LOW_BOUND(var->type)
> $18 = 0
> (top-gdb) p* var->type->main_type
> $33 = {code = TYPE_CODE_ARRAY, upper_bound_type = BOUND_SIMPLE, 
>   lower_bound_type = BOUND_SIMPLE, name = 0x0, tag_name = 0x0, 
>   objfile = 0x8357618, target_type = 0x8372c74, flags = 0, nfields = 1, 
>   vptr_fieldno = -1, fields = 0x837496c, vptr_basetype = 0x0, type_specific = {
>     cplus_stuff = 0x0, floatformat = 0x0}}
> 
> Fortran:
> 
> (top-gdb) p TYPE_LOW_BOUND(var->type)
> $3 = 0
> (top-gdb) p* var->type->main_type
> $8 = {code = TYPE_CODE_ARRAY, upper_bound_type = BOUND_SIMPLE, 
>   lower_bound_type = BOUND_SIMPLE, name = 0x0, tag_name = 0x0, 
>   objfile = 0x8357618, target_type = 0x83654cc, flags = 0, nfields = 1, 
>   vptr_fieldno = -1, fields = 0x83655c4, vptr_basetype = 0x0, 
>   type_specific = {cplus_stuff = 0x0, floatformat = 0x0}}
> 
> I need more of a clue to follow your suggestion.

Well, that's what was SUPPOSED to happen, anyway.

 <1><a52>: Abbrev Number: 4 (DW_TAG_array_type)
     DW_AT_sibling     : <a62>  
     DW_AT_type        : <a62>  
 <2><a5b>: Abbrev Number: 5 (DW_TAG_subrange_type)
     DW_AT_type        : <a62>  
     DW_AT_upper_bound : 4      

I would have expected there to be a lower bound also... but there just
isn't.  Your patch is more or less OK.  Let me reply to it to pick up
some formatting comments.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-06-30 13:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 21:28 Nick Roberts
2005-06-30  2:53 ` Daniel Jacobowitz
2005-06-30  9:28   ` Nick Roberts
2005-06-30 13:15     ` Daniel Jacobowitz [this message]
2005-06-30 22:21       ` Nick Roberts
2005-06-30 22:23         ` Daniel Jacobowitz
2005-06-30 13:18 ` Daniel Jacobowitz
2005-06-30 22:21   ` Nick Roberts
2005-07-01  3:35     ` Wu Zhou
2005-07-01  5:04       ` Nick Roberts
2005-07-01 12:00         ` Wu Zhou
2005-07-03 16:17         ` Daniel Jacobowitz
2005-07-03 23:40           ` Nick Roberts
2005-07-03 23:47             ` Daniel Jacobowitz
2005-07-04  1:42               ` Nick Roberts
2005-07-04  3:49                 ` Daniel Jacobowitz
2005-07-04  7:35                   ` Nick Roberts
2005-07-05  3:43                   ` Nick Roberts
2006-03-13 14:08                   ` Nick Roberts
2006-03-24 22:58                     ` Daniel Jacobowitz
2006-03-27  1:25                       ` Nick Roberts
2006-03-27  4:04                         ` Daniel Jacobowitz
2006-03-27  4:24                           ` Nick Roberts
2006-03-27 11:32                             ` Daniel Jacobowitz
2005-07-06  8:31           ` Wu Zhou

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=20050630131454.GA8241@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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