From: Daniel Jacobowitz <drow@mvista.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: long long considered harmful?
Date: Tue, 22 Apr 2003 19:31:00 -0000 [thread overview]
Message-ID: <20030422193151.GB25488@nevyn.them.org> (raw)
In-Reply-To: <07ce01c308fe$d6ae2c00$0202040a@catdog>
On Tue, Apr 22, 2003 at 02:41:51PM -0400, Kris Warkentin wrote:
> > > > This is a target entity isn't it? You've got no business using
> > > > "double" for a target float. Use the gdb type mechanism instead.
> > >
> > > Can you point to an example of how this is done?
> >
> > Check out floatformat_to_doublest. You may not even need it if you
> > only pass the data to supply_register...
>
> Exactly. All we do is throw the bits around to supply register. I'm just
> looking for a way to make the structures the right size without being
> completely ugly.
If you want structures to be a particular size, you have to either
construct them using the type machinery or else just treat them as a
list of offsets and a size (all ints). There's really nothing else
portable. C'mon, I'll introduce you to a 32-bit-char host for fun and
see how you like it.
> Well, at the moment, the only host we build gdb for is i386 and Sparc
> (Neutrino, Solaris and Win32) but conceivably we might want to build a gdb
> for Neutrino on ppc or mips or some such. Once again, as far as gdb is
> concerned, none of it really matters because this is just data coming over
> the wire (or from a system call) and all it needs to know is which offset
> into the structure to call supply_register on.
Record only the offsets, then.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-04-22 19:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 17:39 Kris Warkentin
2003-04-22 17:45 ` Daniel Jacobowitz
2003-04-22 18:08 ` Kris Warkentin
2003-04-22 18:21 ` Daniel Jacobowitz
2003-04-22 18:41 ` Kris Warkentin
2003-04-22 19:31 ` Daniel Jacobowitz [this message]
2003-04-22 19:12 ` Kris Warkentin
2003-04-22 19:25 ` Kris Warkentin
2003-04-22 19:30 ` Daniel Jacobowitz
2003-04-23 13:39 ` Kris Warkentin
2003-04-23 21:17 ` Daniel Jacobowitz
2003-04-23 21:23 ` Kris Warkentin
2003-04-23 21:44 ` Kris Warkentin
2003-04-23 21:47 ` Daniel Jacobowitz
2003-04-23 22:09 ` Kris Warkentin
2003-04-23 22:11 ` Daniel Jacobowitz
2003-04-23 22:17 ` Kris Warkentin
2003-04-24 21:05 ` Andrew Cagney
2003-04-24 23:51 ` Kris Warkentin
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=20030422193151.GB25488@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.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