Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: luisgpm@linux.vnet.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Improve printf DFP support
Date: Tue, 08 Jan 2008 15:19:00 -0000	[thread overview]
Message-ID: <1199805546.15225.8.camel@localhost.localdomain> (raw)
In-Reply-To: <1199798856.22083.9.camel@gargoyle>

On Tue, 2008-01-08 at 11:27 -0200, Luis Machado wrote:
> Comments?

> +	      gdb_byte *param_ptr = (gdb_byte *) value_contents_all >
(val_args[i])
>                                        + value_offset (val_args[i]);

param_ptr should be a const gdb_byte *, and the cast here should be
removed. In addition, I believe the use of value_offset here is wrong.
Other uses of value_offset are to obtain a memory address in the
inferior address space, not in GDB's. Also, I think that value_contents
should be used intead of value_contents_all so that the value's
embedded_offset can be taken into account.

> +	      dfp_ptr = (gdb_byte *) value_contents_all (dfp_value)
> +				      + value_offset (dfp_value);

Same here.

PS: I don't have deep understaing of GDB's value mechanism so if someone
sees I am saying something wrong here please correct me.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center


  reply	other threads:[~2008-01-08 15:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 13:28 Luis Machado
2008-01-08 15:19 ` Thiago Jung Bauermann [this message]
2008-01-08 15:29   ` Daniel Jacobowitz
2008-01-08 23:54     ` Jim Blandy
2008-01-08 15:29   ` Luis Machado
2008-01-08 20:42 ` Eli Zaretskii
2008-01-09  0:04   ` Luis Machado
2008-01-09  4:14     ` Eli Zaretskii
2008-01-09 12:52     ` Daniel Jacobowitz
2008-01-09 13:51       ` Luis Machado

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=1199805546.15225.8.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.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