public inbox for
 help / color / mirror / Atom feed
From: Kevin Buettner <>
Subject: Re: [RFC] Revise interfaces for *_bytes_{from,to}_reg()
Date: Wed, 27 Nov 2002 14:02:00 -0000	[thread overview]
Message-ID: <1021127220214.ZM32427@localhost.localdomain> (raw)
In-Reply-To: Kevin Buettner <> "Re: [RFC] Revise interfaces for *_bytes_{from,to}_reg()" (Nov 27, 11:49am)

On Nov 27, 11:49am, Kevin Buettner wrote:

> I'm considering adding gdbserv_{host,le,be}_signed_bytes_{to,from}_reg().
> Another approach is to add a parameter (flag) to the existing functions
> which indicate whether signed or unsigned extension should be done.

I've decided to add a ``sign_extend'' parameter to these functions.


      reply	other threads:[~2002-11-27 22:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-27 10:33 Kevin Buettner
2002-11-27 10:49 ` Kevin Buettner
2002-11-27 14:02   ` Kevin Buettner [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1021127220214.ZM32427@localhost.localdomain \ \ \

* 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).