From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug in asm.ps
Date: Mon, 6 Mar 2006 11:17:52 -0500 [thread overview]
Message-ID: <c44e01d0f480a2fba457c2756dd7140b@swtch.com> (raw)
In-Reply-To: <dc32fda15071d82aa3d6be853eac99c5@coraid.com>
I still don't know what you think is wrong.
Are you referring to the order in which stack
variables are allocated in the stack frame?
(I thought you were referring to the placement
of temporaries to hold function call parameters.)
All the compilers allocate their stack frames the
same way, as far as I can tell. But I don't see
asm.ps making claims about what the correspondence
between assembly and C is. First and last
depend on your point of view.
Russ
next prev parent reply other threads:[~2006-03-06 16:17 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
2006-03-06 16:17 ` Russ Cox [this message]
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=c44e01d0f480a2fba457c2756dd7140b@swtch.com \
--to=rsc@swtch.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).