From: "Jim Blandy" <jimb@red-bean.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: "Jim Blandy" <jimb@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [rfc] Make DWARF-2 "address size" explicit
Date: Tue, 29 Jan 2008 03:42:00 -0000 [thread overview]
Message-ID: <8f2776cb0801281749w734a3d9h5386a493fb2c2bfb@mail.gmail.com> (raw)
In-Reply-To: <200801141554.m0EFskPB011384@d12av02.megacenter.de.ibm.com>
On Jan 14, 2008 7:54 AM, Ulrich Weigand <uweigand@de.ibm.com> wrote:
> Apart from that, the behaviour should be identical, with one
> exception: what address size to use for CFI. Your patch uses
> size_of_encoded_value (DW_EH_PE_absptr)
> which basically boils down to:
> gdbarch_ptr_bit (current_gdbarch) / TARGET_CHAR_BIT
>
> This would be an effective change in behaviour to what we have
> now, which is:
> gdbarch_addr_bit (current_gdbarch) / TARGET_CHAR_BIT
>
> My patch uses in effect
> gdbarch_addr_bit (get_frame_arch (frame)) / TARGET_CHAR_BIT
> which does not change behaviour.
>
> However, it might well be that the original code is simply wrong
> and we *should* be using ...ptr_bit instead of ...addr_bit.
> What do you think?
(Sorry --- I thought I had replied to this.)
I don't think any change my patch made to the value used there was
intentional. Whatever you have determined is the best value to use
there is more likely to be right than whatever is in my patch. I
don't think this difference is a problem.
prev parent reply other threads:[~2008-01-29 1:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 19:40 Ulrich Weigand
2007-12-16 22:04 ` Daniel Jacobowitz
2007-12-17 20:06 ` Jim Blandy
2008-01-14 15:55 ` Ulrich Weigand
2008-01-28 21:08 ` Ulrich Weigand
2008-01-28 23:48 ` Daniel Jacobowitz
2008-01-29 19:00 ` Ulrich Weigand
2008-01-29 3:42 ` Jim Blandy [this message]
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=8f2776cb0801281749w734a3d9h5386a493fb2c2bfb@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=uweigand@de.ibm.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