Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sources.redhat.com
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: [patch] XLF Fortran: Remove an inappropriate complaint
Date: Mon, 26 Nov 2007 07:20:00 -0000	[thread overview]
Message-ID: <20071126072041.GA16110@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20071125221357.GA20375@caradoc.them.org>

[-- Attachment #1: Type: text/plain, Size: 2276 bytes --]

On Sun, 25 Nov 2007 23:13:57 +0100, Daniel Jacobowitz wrote:
...
> I'm confused.  What's wrong?
> 
> The patch I was replying to removed the complaint call.  That seems
> fine, since it isn't related to DW_FORM_ref* support.

The attached file (a binary patched one GCC output) should have for
DW_TAG_array_type <7a>:

According to the DWARF3 spec: index type `short int'.

Current CVS HEAD GDB complains and assigns: index type `long int' (64-bit int).

Therefore GDB violates the DWARF3 spec and the complaint there is right as it
warns the user GDB has violated the DWARF3 spec while parsing the ELF file.



Regards,
Jan


Contents of the .debug_abbrev section:

  Number TAG
   2      DW_TAG_variable    [no children]
    DW_AT_name         DW_FORM_string
    DW_AT_decl_file    DW_FORM_data1
    DW_AT_decl_line    DW_FORM_data1
    DW_AT_type         DW_FORM_ref4
    DW_AT_external     DW_FORM_flag
    DW_AT_location     DW_FORM_block1
   3      DW_TAG_base_type    [no children]
    DW_AT_name         DW_FORM_string
    DW_AT_byte_size    DW_FORM_data1
    DW_AT_encoding     DW_FORM_data1
   4      DW_TAG_array_type    [has children]
    DW_AT_sibling      DW_FORM_ref4
    DW_AT_type         DW_FORM_ref4
   5      DW_TAG_subrange_type    [no children]
    DW_AT_upper_bound  DW_FORM_ref1
    DW_AT_visibility   DW_FORM_data4

The section .debug_info contains:

  Compilation Unit @ offset 0x0:
   Pointer Size:  8
 <1><55>: Abbrev Number: 2 (DW_TAG_variable)
  <56>     DW_AT_name        : bound	
  <5c>     DW_AT_decl_file   : 1	
  <5d>     DW_AT_decl_line   : 1	
  <5e>     DW_AT_type        : <6d>	
  <62>     DW_AT_external    : 1	
  <63>     DW_AT_location    : 9 byte block: 3 0 0 0 0 0 0 0 0 	(DW_OP_addr: 0)
 <1><6d>: Abbrev Number: 3 (DW_TAG_base_type)
  <6e>     DW_AT_name        : short int	
  <78>     DW_AT_byte_size   : 2	
  <79>     DW_AT_encoding    : 5	(signed)
 <1><7a>: Abbrev Number: 4 (DW_TAG_array_type)
  <7f>     DW_AT_type        : <9f>	
 <2><83>: Abbrev Number: 5 (DW_TAG_subrange_type)
  <84>     DW_AT_upper_bound : <55>	
  <85>     DW_AT_visibility  : 0x2	(exported)
 <1><9f>: Abbrev Number: 3 (DW_TAG_base_type)
  <a0>     DW_AT_name        : char	
  <a5>     DW_AT_byte_size   : 1	
  <a6>     DW_AT_encoding    : 6	(signed char)

[-- Attachment #2: type-var.o.gz --]
[-- Type: application/x-gzip, Size: 652 bytes --]

  reply	other threads:[~2007-11-26  7:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16  3:20 [00/11] Fortran dynamic arrays support Jan Kratochvil
2007-11-16 17:46 ` Jim Blandy
2007-11-16 17:55 ` Carlos Eduardo Seo
2007-11-16 19:45   ` Jan Kratochvil
2007-11-19 14:41     ` Carlos Eduardo Seo
     [not found]       ` <20071123015957.GA3202@host0.dyn.jankratochvil.net>
     [not found]         ` <20071123021120.GA11797@host0.dyn.jankratochvil.net>
     [not found]           ` <20071123163125.GA23275@host0.dyn.jankratochvil.net>
     [not found]             ` <4747086C.3070100@linux.vnet.ibm.com>
2007-11-23 17:21               ` [patch] XLF Fortran: Remove an inappropriate complaint [Re: XLF Fortran arrays test] Jan Kratochvil
2007-11-25 14:56                 ` Daniel Jacobowitz
2007-11-25 22:11                   ` Jan Kratochvil
2007-11-25 22:14                     ` Daniel Jacobowitz
2007-11-26  7:20                       ` Jan Kratochvil [this message]
2007-11-26 13:26                         ` [patch] XLF Fortran: Remove an inappropriate complaint Daniel Jacobowitz
2007-11-26 22:07                           ` Jan Kratochvil

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=20071126072041.GA16110@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=drow@false.org \
    --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