public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hariharans at picochip dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/47946] New: Dwarf uses 64-bits to refer to a structure offset unnecessarily
Date: Tue, 01 Mar 2011 15:31:00 -0000	[thread overview]
Message-ID: <bug-47946-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47946

           Summary: Dwarf uses 64-bits to refer to a structure offset
                    unnecessarily
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hariharans@picochip.com


Created attachment 23503
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23503
The source code

Hello,
In the attached testcase, our dwarf reader reports the structure as

Abbrevation 2: DW_TAG_structure_type [has children]
  DW_AT_name            DW_FORM_string
  DW_AT_byte_size               DW_FORM_data1
  DW_AT_decl_file               DW_FORM_data1
  DW_AT_decl_line               DW_FORM_data1
  DW_AT_sibling         DW_FORM_ref4
Abbrevation 3: DW_TAG_member
  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_byte_size               DW_FORM_data1
  DW_AT_bit_size                DW_FORM_data1
  DW_AT_bit_offset              DW_FORM_data1
  DW_AT_data_member_location            DW_FORM_block1
Abbrevation 4: DW_TAG_member
  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_byte_size               DW_FORM_data1
  DW_AT_bit_size                DW_FORM_data1
  DW_AT_bit_offset              DW_FORM_data8
  DW_AT_data_member_location            DW_FORM_block1

Note that the first element (c1) takes a DW_FORM_data1 to represent the offset,
whereas the second (i) uses DW_FORM_data8. I am fairly certain it doesn't need
64-bits to represent the offset, so something is wrong here.

I tested this with picochip port in the mainline GCC (as of 03-feb-2011).


             reply	other threads:[~2011-03-01 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01 15:31 hariharans at picochip dot com [this message]
2011-03-01 15:31 ` [Bug debug/47946] " hariharans at picochip dot com
2011-03-01 17:07 ` matz at gcc dot gnu.org
2011-03-01 18:39 ` jakub at gcc dot gnu.org
2011-03-02 10:11 ` hariharans at picochip dot com
2011-03-14 20:07 ` jakub at gcc dot gnu.org
2011-03-14 20:13 ` jakub at gcc dot gnu.org

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=bug-47946-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).