9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] update a.out manpage to be 64 bit inclusive
Date: Wed, 09 Jun 2021 23:05:10 -0400	[thread overview]
Message-ID: <031E3BA99801F96A5256D5E30EE463BB@eigenstate.org> (raw)
In-Reply-To: <33B60BAB203E253CB0ADF62326A8CB5D@gmail.com>

Quoth jacob gw <jacoblevgw@gmail.com>:
> ---
> diff fd9679d97b0bb7b8849f84f50c708d5f733708e1 ea21c85c5ced615ab90d7efca9a100596cf71333
> --- a/sys/man/6/a.out	Sat Jun  5 09:40:28 2021
> +++ b/sys/man/6/a.out	Sat Jun  5 14:48:10 2021
> @@ -52,6 +52,10 @@
>  Sizes are expressed in bytes.
>  The size of the header is not included in any of the other sizes.
>  .PP
> +There may be an extra 8 bytes after the header on 64 bit systems.
> +These bytes represent the entry point in a 64 bit address space.
> +You can tell that these will be there if magic & HDR_MAGIC.

How about this wording?

When HDR_MAGIC is set, an 8 byte entry point
is included in the header. This is used in
place of the 4 byte header.

> +.PP
>  When a Plan 9 binary file is executed,
>  a memory image of three segments is
>  set up: the text segment, the data segment, and the stack.
> @@ -93,7 +97,7 @@
>  entries, each laid out as:
>  .IP
>  .EX
> -uchar value[4];
> +uchar value[4]; /* value[8] on 64 bit systems */
>  char  type;
>  char  name[\f2n\fP];   /* NUL-terminated */
>  .EE
> @@ -141,6 +145,9 @@
>  .TP
>  .B p
>  function parameter symbol
> +.TP
> +.B m
> +frame symbol
>  .RE
>  .PD
>  .PP
> 


      reply	other threads:[~2021-06-13  0:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-05 18:48 jacob gw
2021-06-10  3:05 ` ori [this message]

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=031E3BA99801F96A5256D5E30EE463BB@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).