From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug in asm.ps
Date: Mon, 6 Mar 2006 11:05:39 -0500 [thread overview]
Message-ID: <dc32fda15071d82aa3d6be853eac99c5@coraid.com> (raw)
In-Reply-To: <fa27b3307cfc3f25dc2c342741d61af5@swtch.com>
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
I've never made a mistake... I once thought I had, but was wrong.
I forgot that it was talking about the '020.
That context thing. :)
I kind of like the way that 8c allocates them. That means that
I could dump &first to the &last and see the local stack frame.
It struck me years ago that the stack frame was just an implied
structure.
Might be mentioned in the 8a section, though.
[-- Attachment #2: Type: message/rfc822, Size: 2734 bytes --]
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug in asm.ps
Date: Mon, 6 Mar 2006 10:53:55 -0500
Message-ID: <fa27b3307cfc3f25dc2c342741d61af5@swtch.com>
> Oh, I understand now. You are correct. Asm.ps is wrong.
What exactly do you think is wrong?
(And keep in mind that page 1 is explicitly
marked as a discussion of 2a.)
Russ
next prev parent reply other threads:[~2006-03-06 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 15:12 Gorka guardiola
2006-03-06 15:16 ` Brantley Coile
2006-03-06 15:31 ` Gorka guardiola
2006-03-06 15:36 ` Brantley Coile
2006-03-06 15:53 ` Russ Cox
2006-03-06 16:05 ` Brantley Coile [this message]
2006-03-06 16:17 ` Russ Cox
2006-03-06 16:22 ` Brantley Coile
2006-03-06 16:28 ` Russ Cox
2006-03-06 16:33 ` Gorka guardiola
2006-03-06 16:56 ` Charles Forsyth
2006-03-06 16:16 ` Gorka guardiola
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=dc32fda15071d82aa3d6be853eac99c5@coraid.com \
--to=brantley@coraid.com \
--cc=9fans@cse.psu.edu \
/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).