From: Pedro Alves <palves@redhat.com>
To: Jerome Guitton <guitton@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] setting the raw content of a register
Date: Tue, 22 May 2012 16:32:00 -0000 [thread overview]
Message-ID: <4FBBBF75.4040605@redhat.com> (raw)
In-Reply-To: <20120522152459.GQ51051@adacore.com>
On 05/22/2012 04:24 PM, Jerome Guitton wrote:
> Pedro Alves (palves@redhat.com):
>
>> What about :
>>
>> p $f14 = {double} {0xFFF0000000000050}
>
> I've been testing with a bareboard PPC, and this needs malloc;
Hmm, looks like you're right. I was almost certain there was a way
to avoid the malloc if the cast/conversion is done to a type of
the exact same size as the source array, but it's escaping me now
how.
--
Pedro Alves
next prev parent reply other threads:[~2012-05-22 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 14:37 Jerome Guitton
2012-05-22 14:55 ` Pedro Alves
2012-05-22 15:25 ` Jerome Guitton
2012-05-22 16:32 ` Pedro Alves [this message]
2012-05-23 15:22 ` Doug Evans
2012-05-23 15:28 ` Pedro Alves
2012-05-23 15:42 ` Jerome Guitton
2012-05-23 16:03 ` Pedro Alves
2012-05-23 16:10 ` Pedro Alves
2012-05-23 16:22 ` Joel Brobecker
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=4FBBBF75.4040605@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.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