From: Nick Clifton <nickc@redhat.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: "'Kai Tietz'" <ktietz70@googlemail.com>,
"'H.J. Lu'" <hjl.tools@gmail.com>,
"'Binutils'" <binutils@sourceware.org>
Subject: Re: [RFC-v2] Use only dwarf_vma types in dwarf code
Date: Fri, 25 Mar 2011 15:16:00 -0000 [thread overview]
Message-ID: <4D8CB1F5.6020108@redhat.com> (raw)
In-Reply-To: <00d601cbd4f0$c911af10$5b350d30$@muller@ics-cnrs.unistra.fr>
Hi Pierre,
[only a month late...]
> 2011-02-25 Pierre Muller<muller@ics.u-strasbg.fr>
>
> Replace bfd_vma type and analog types by dwarf_vma and analogs.
> Use dwarf specific print functions to display these type values.
> * dwarf.h (dwarf_signed_vma): New type;
> (DWARF2_External_LineInfo): Replace bfd_vma by dwarf_vma.
> (DWARF2_External_PubNames): Likewise.
> (DWARF2_External_CompUnit): Likewise.
> (DWARF2_External_ARange): Likewise.
> (read_leb128): Change return type to dwarf_vma.
> * dwarf.c (print_dwarf_vma): Use __MINGW32__ conditional and
> check byte_size values.
> (dwarf_vmatoa): Change parameter type to dwarf_vma.
> (dwarf_svmatoa): New static function.
> (read_leb128): Change return type to dwarf_vma.
> (read_sleb128): New static function.
> (struct State_Machine_Registers): Change address field type to
> dwarf_vma.
> (process_extended_line_op): Adapt to type changes.
> (fetch_indirect_string): Likewise.
> (idisplay_block): Likewise.
> (decode_location_expression): Likewise.
> (read_and_display_attr_value): Likewise.
> (process_debug_info): Likewise.
> (display_debug_lines_raw): Likewise.
> (display_debug_lines_decoded): Likewise.
> (SLEB macro): Use new read_sleb128 function.
Approved and applied - along with a little tidying up.
Cheers
Nick
next prev parent reply other threads:[~2011-03-25 15:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 14:21 [RFC patch]: Adjust the use of 'long' type in dwarf2.h header Kai Tietz
2011-02-17 18:59 ` Kai Tietz
2011-02-17 19:03 ` Jakub Jelinek
2011-02-17 19:07 ` Kai Tietz
2011-02-17 19:17 ` Jakub Jelinek
2011-02-18 9:50 ` Kai Tietz
2011-02-21 12:37 ` NightStrike
2011-02-21 13:10 ` Pierre Muller
[not found] ` <-8460070221060995487@unknownmsgid>
2011-02-21 13:27 ` Kai Tietz
2011-02-21 13:46 ` Pierre Muller
[not found] ` <-6930711422310680743@unknownmsgid>
2011-02-21 14:30 ` Kai Tietz
2011-02-21 15:25 ` Kai Tietz
2011-02-21 15:43 ` Mark Kettenis
2011-02-21 15:53 ` Kai Tietz
2011-02-22 15:21 ` Nick Clifton
2011-02-23 8:59 ` Kai Tietz
2011-02-23 15:12 ` Pierre Muller
[not found] ` <-2339605939192327273@unknownmsgid>
2011-02-23 17:42 ` Kai Tietz
2011-02-23 21:55 ` Pierre Muller
[not found] ` <-3886800211494155692@unknownmsgid>
2011-02-23 22:51 ` H.J. Lu
2011-02-24 11:33 ` Pierre Muller
[not found] ` <1561346207520594884@unknownmsgid>
2011-02-24 13:50 ` H.J. Lu
2011-02-25 10:40 ` [RFC] Use only dwarf_vma types in dwarf code (was RE: [RFC patch]: Adjust the use of 'long' type in dwarf2.h header) Pierre Muller
[not found] ` <5095785081977025060@unknownmsgid>
2011-02-25 12:23 ` Kai Tietz
2011-02-25 13:31 ` Pierre Muller
2011-02-25 13:35 ` [RFC-v2] Use only dwarf_vma types in dwarf code Pierre Muller
2011-03-25 15:16 ` Nick Clifton [this message]
2011-03-25 15:48 ` [RFA] Supplemtal patch for use " Pierre Muller
2011-03-25 18:04 ` Nick Clifton
2011-03-25 21:44 ` Pierre Muller
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=4D8CB1F5.6020108@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=ktietz70@googlemail.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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).