Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: File-I/O patch, Documentation
Date: Fri, 28 Feb 2003 16:37:00 -0000	[thread overview]
Message-ID: <20030228163755.GA24652@nevyn.them.org> (raw)
In-Reply-To: <20030228154926.GL20955@cygbert.vinschen.de>

On Fri, Feb 28, 2003 at 04:49:26PM +0100, Corinna Vinschen wrote:
> On Fri, Feb 28, 2003 at 10:25:04AM -0500, Daniel Jacobowitz wrote:
> > On Fri, Feb 28, 2003 at 09:33:08AM +0100, Corinna Vinschen wrote:
> > > > c99 (what ever the standard) formalized a number of explicitly sized 
> > > > types (int32 et.al. I believe).  I think this table should be specified 
> > > > using those types.  The alternative is to generalize the 
> > > > sim/common/sim-types.h file and then specify the sizes using that.
> > > 
> > > I don't think so.  The protocol is more or less self-contained.  All
> > > definitions are based on the assumption, that you'll never find a
> > > really matching combination of values as they are defined on all
> > > machines.  Looking into the fileio code you'll see, that gdb has a
> > > couple of functions which transform all protocol datatypes to host
> > > datatypes and all protocol values to host values and vice versa.
> > > This is done that way to be totally independent from other sources of
> > > definition (especially machine dependent definitions).
> > > 
> > > It's *expected* that the gdb plugin on the target side is doing the
> > > same.
> > 
> > Sure.  But how big are they on the wire?  I think that's what Andrew
> > was asking to be clarified.
> 
> ...which is written into the document in the chapter "Integral datatypes"
> which I mistakenly referenced as "B.1" as it was in my original document
> I've send months ago on the gdb ML.

Sorry.  I was extrapolating from Andrew's answer, and it's been months
since I read it.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-28 16:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21  1:04 Corinna Vinschen
2002-11-21  1:22 ` Corinna Vinschen
2002-11-23  3:04   ` Eli Zaretskii
2002-11-23  3:02 ` Eli Zaretskii
2002-11-23  8:12   ` Andrew Cagney
2002-11-25  2:52   ` Corinna Vinschen
2002-11-25 11:01     ` Eli Zaretskii
2002-11-26  6:07       ` Corinna Vinschen
2002-11-26 10:02         ` Eli Zaretskii
2002-11-27  9:08           ` Corinna Vinschen
2003-02-26 23:20 ` Andrew Cagney
2003-02-27  8:37   ` Corinna Vinschen
2003-02-27 23:05     ` Andrew Cagney
2003-02-28  8:33       ` Corinna Vinschen
2003-02-28 15:25         ` Daniel Jacobowitz
2003-02-28 15:49           ` Corinna Vinschen
2003-02-28 16:37             ` Daniel Jacobowitz [this message]
2003-02-28 15:27         ` Andrew Cagney
2003-02-28 15:47           ` Corinna Vinschen
2003-03-02  3:03             ` Andrew Cagney
2003-03-03 12:12               ` Corinna Vinschen
2003-03-04 18:53                 ` Andrew Cagney
2003-03-04 19:46                   ` Eli Zaretskii
2003-03-06 21:19                     ` Andrew Cagney
2003-03-06 21:26                 ` Andrew Cagney
2003-03-07 14:29                   ` Corinna Vinschen
2003-03-07 14:55                     ` Andrew Cagney
2003-03-01 12:36     ` Eli Zaretskii
2003-03-01 15:43       ` Andrew Cagney

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=20030228163755.GA24652@nevyn.them.org \
    --to=drow@mvista.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