From: Andrew Cagney <ac131313@redhat.com>
To: Corinna Vinschen <vinschen@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: File-I/O patch, Documentation
Date: Thu, 27 Feb 2003 23:05:00 -0000 [thread overview]
Message-ID: <3E5E9A1A.9000708@redhat.com> (raw)
In-Reply-To: <20030227083701.GE20955@cygbert.vinschen.de>
> +@menu
> +* File-I/O Overview::
> +* Protocol basics::
> +* The `F' request packet::
> +* The `F' reply packet::
> +* Memory transfer::
> +* The Ctrl-C message::
> +* Console I/O::
> +* The isatty call::
> +* The system call::
> +* List of supported calls::
I think the only problem here is the need for two small, simple but
concrete examples:
- the target doing a write() call
- the user entering CNTRL-C and a demonstration of one of the edge cases
> +* Protocol specific representation of datatypes::
> +* Constants::
> +@end menu
--
My one concern with the protocol spec is with this structure. The size
of those various types is target compiler dependent yet the
implementation assumes specific sizes.
> +@smallexample
> +struct stat @{
> + unsigned int st_dev; /* device */
> + unsigned int st_ino; /* inode */
> + mode_t st_mode; /* protection */
> + unsigned int st_nlink; /* number of hard links */
> + unsigned int st_uid; /* user ID of owner */
> + unsigned int st_gid; /* group ID of owner */
> + unsigned int st_rdev; /* device type (if inode device) */
> + unsigned long st_size; /* total size, in bytes */
> + unsigned long st_blksize; /* blocksize for filesystem I/O */
> + unsigned long st_blocks; /* number of blocks allocated */
> + time_t st_atime; /* time of last access */
> + time_t st_mtime; /* time of last modification */
> + time_t st_ctime; /* time of last change */
> +@};
> +@end smallexample
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.
The time unit of st_*time should be defined.
The byte order of all the values should be defined.
The reference to B.1 should be removed.
Andrew
next prev parent reply other threads:[~2003-02-27 23:05 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 [this message]
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
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=3E5E9A1A.9000708@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vinschen@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