9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "James A. Robinson" <jim.robinson@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] /sys/src/9/port/portfns.h execregs uint vs ulong
Date: Fri,  4 Nov 2016 23:09:05 +0000	[thread overview]
Message-ID: <CAPd04b6w-M9bktCNMZaxY=etBZoQv0NfyKQ2RY7ZfQMgN1AKyw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 601 bytes --]

While futzing around with rebuilding a kernel, I noticed that
9atom distributed source tree /sys/src/9/port/portfns.h
declares

void* execregs(uintptr, uint, uint)

but /sys/src/9/pc/trap.c declares

long
execregs(ulong entry, ulong ssize, ulong nargs)

which seems to match all the other architectures
I see under /sys/src/9/.

I can't get to http://plan9.bell-labs.com/sources/
right now, it looks to be offline (I hope me looking
at the wiki and man pages via http earlier wasn't
"too high traffic" for it...), but wondered if this was
an oversight in updating portfns.h.

Jim

[-- Attachment #2: Type: text/html, Size: 921 bytes --]

                 reply	other threads:[~2016-11-04 23:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAPd04b6w-M9bktCNMZaxY=etBZoQv0NfyKQ2RY7ZfQMgN1AKyw@mail.gmail.com' \
    --to=jim.robinson@gmail.com \
    --cc=9fans@9fans.net \
    /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).