Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Question: Checking register value in buffer
Date: Thu, 19 May 2005 16:41:00 -0000	[thread overview]
Message-ID: <428CA4A1.8020408@gnu.org> (raw)
In-Reply-To: <20050519020443.GP1462@adacore.com>

Joel Brobecker wrote:
> Hello,
> 
> I'm wondering if there is a usual way for what I'm trying to do.
> Basically, I have fetched a 64bit floating point register on alpha
> using:

Have you looked at doublest.[hc]?

>       regcache_cooked_read (current_regcache, (insn >> 21) & 0x1f, reg);
> 
> where reg is a ``char reg[8]''.
> 
> Now, I'd like to perform the following tests:
> 
>   zero          (reg & 0x7fff_ffff_ffff_ffff) == 0
>   sign          (reg & 0x8000_0000_0000_0000) != 0
> 
> Right now, I'm juggling with each byte of the buffer, and doing checks
> like this:
> 
>     fp_register_zero_p (char *buf)
>     {
>       return ((buf[1] & 0x0f) == 0 && buf[2] == 0 && buf[3] == 0
>               && buf[4] == 0 && buf[5] == 0 && buf[6] == 0 && buf[7] == 0);
> 
> I thought about something like:
> 
>         LONGEST rav = extract_signed_integer (buf, 8)
> 
> and then do the test using integer arithmetics. But then I'm not guarantied
> that LONGEST is at least 64bit long, am I.
> 
> How are these sort of checks usually done in GDB?
> 
> Thanks,


      parent reply	other threads:[~2005-05-19 14:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  2:49 Joel Brobecker
2005-05-19  3:03 ` Richard Henderson
2005-05-19  3:07   ` Joel Brobecker
2005-05-19  3:23     ` Richard Henderson
2005-05-19  3:33       ` Joel Brobecker
2005-05-19  4:52         ` Richard Henderson
2005-05-19  5:37         ` Daniel Jacobowitz
2005-05-19  3:26   ` Daniel Jacobowitz
2005-05-19 16:41 ` Andrew Cagney [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=428CA4A1.8020408@gnu.org \
    --to=cagney@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.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