Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: gdb@sourceware.org
Subject: Re: GDB printf command
Date: Tue, 17 Oct 2006 14:43:00 -0000	[thread overview]
Message-ID: <4534EC06.3050200@st.com> (raw)
In-Reply-To: <20061017142451.GA30620@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Tue, Oct 17, 2006 at 03:09:03PM +0100, Andrew STUBBS wrote:
>> The expression parser/evaluator must use host types at some level. Does 
>> this not have similar horrors hidden away? If this can convert target 
>> types to host types (of at least the same precision) can the printf not 
>> be implemented with the same mapping somehow?
> 
> Well, I suppose all we need to do is appropriate widening.  We can pass
> everything to the host code as LONGESTs and DOUBLESTs.
> 
> Are you interested in working on this?  If so, I can quickly pull
> together a patch to add the printf backend that I was thinking of;
> all it'll need is glue.

I'm not really sure what you are suggesting I do exactly. What do you 
think ought to be done and where?

How much effort do you think it will take? Like everyone else I don't 
have enormous amounts of time for projects I wasn't expecting.

Assuming it isn't a big task I am certainly interested in getting it 
done right. Whatever that is, hopefully it does include the same target 
working the same on all hosts (or at least all the same features 
working, for some definition of 'work').

Andrew


  reply	other threads:[~2006-10-17 14:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 12:03 Andrew STUBBS
2006-10-17 13:24 ` Daniel Jacobowitz
2006-10-17 14:10   ` Andrew STUBBS
2006-10-17 14:25     ` Daniel Jacobowitz
2006-10-17 14:43       ` Andrew STUBBS [this message]
2006-10-17 14:54         ` Daniel Jacobowitz
2006-10-18 11:24           ` Andrew STUBBS
2006-10-18 13:53             ` Daniel Jacobowitz
2006-10-31 11:43             ` Andrew STUBBS
2006-10-31 13:42               ` Daniel Jacobowitz

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=4534EC06.3050200@st.com \
    --to=andrew.stubbs@st.com \
    --cc=gdb@sourceware.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