Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Bart Veer <bartv@ecoscentric.com>, gdb-patches@sourceware.org
Subject: Re: minor doc fix
Date: Wed, 30 Jul 2008 18:49:00 -0000	[thread overview]
Message-ID: <20080730184902.GA25746@caradoc.them.org> (raw)
In-Reply-To: <uvdynnrvk.fsf@gnu.org>

On Wed, Jul 30, 2008 at 09:34:07PM +0300, Eli Zaretskii wrote:
> > Date: Wed, 30 Jul 2008 19:17:02 +0100
> > From: Bart Veer <bartv@ecoscentric.com>
> > CC: gdb-patches@sourceware.org
> > 
> > The text is not talking about host-side or target-side data
> > structures. It is describing a protocol, what gets transferred between
> > host and target for a gettimeofday request, which happens to be 12
> > bytes and not 8.
> 
> Sorry, you lost me.  Perhaps I'm confused, but `long' takes 8 bytes
> only on 64-bit Unix machines.  Otherwise it's 4 bytes.  What am I
> missing?

The answer's even in the manual! :-)

In Protocol-specific Representation of Datatypes, see Integral
Datatypes:

   `long' and `unsigned long' are implemented as 64 bit types.

Then in struct timeval:

     struct timeval {
         time_t tv_sec;  /* second */
         long   tv_usec; /* microsecond */
     };

     The integral datatypes conform to the definitions given in the
  appropriate section (see *note Integral Datatypes::, for details) so
  this structure is of size 8 bytes.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-07-30 18:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 15:55 Bart Veer
2008-07-30 17:55 ` Eli Zaretskii
2008-07-30 18:17   ` Bart Veer
2008-07-30 18:34     ` Eli Zaretskii
2008-07-30 18:49       ` Daniel Jacobowitz [this message]
2008-07-30 19:08         ` Eli Zaretskii
2008-07-30 19:15           ` Daniel Jacobowitz
2008-07-30 20:28       ` Bart Veer

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=20080730184902.GA25746@caradoc.them.org \
    --to=drow@false.org \
    --cc=bartv@ecoscentric.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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