From: John Reiser <jreiser@bitwagon.com>
To: musl@lists.openwall.com
Subject: Re: [PATCH] Add comments to i386 assembly source
Date: Sat, 30 Dec 2017 20:15:41 -0800 [thread overview]
Message-ID: <72c68934-4445-c83d-7bbc-004953b2f9e9@bitwagon.com> (raw)
In-Reply-To: <20171223094545.rmx6xtmucyz5xzap@voyager>
On 12/23/2017 09:45 UTC, Markus Wichmann wrote:
> But then there's i386. Without comments, and pulling off some very black
> magic, I thought it would be worth commenting the files at least in the
> threads directory.
> - mov $120,%al
> + mov $120,%al /* __NR_clone */
Using an actual symbol is clearer and easier to maintain or modify:
+__NR_clone = 120
+ mov $__NR_clone,%al
Constant arguments to system calls (including the system call number)
should be loaded last in order to provide the least constraints for computing
non-constant arguments. Also, it is not obvious that as values (%eax == %al).
The value in %eax was set by "xor %eax,%eax; ...; mov %gs,%ax; ...; shr $3,%eax";
what guarantees that (%gs <= (255 << 3)) ? %gs could be as high as (8191 << 3).
So _that_ deserves a comment; else for safety all of %eax should be set:
+ push $__NR_clone; pop %eax /* 3 bytes; __NR_clone < 128 */
+ int $128 /* clone(flags, stack, TID pointer, {.index = current gs index, .base = thread pointer, .limit=0xfffff, .seg32_bit, .limit_in_pages, .usable}, td pointer) */
Clarity can be improved by using a symbol:
NBPW = 4 /* Number of Bytes Per Word */
mov 3*NBPW(%ebp),%ecx /* ecx = stack */
mov 4*NBPW(%ebp),%ebx /* ebx = flags */
etc.
Incorrect comment:
> + sub $16,%ecx /* align stack */
Perhaps you meant "/* allocate space for returned segment descriptor */"?
The alignment is performed by:
and $-4*NBPW,%ecx /* align for stack */
If you are aiming for small space then
+ mov %eax,%ebx /* exit(rv from function) */
can be implemented one byte smaller as:
+ xchg %eax,%ebx /* syscall arg %ebx = rv from function; %eax = do not care */
--
next prev parent reply other threads:[~2017-12-31 4:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 9:45 Markus Wichmann
2017-12-31 4:15 ` John Reiser [this message]
2017-12-31 6:54 ` Markus Wichmann
2017-12-31 15:49 ` Rich Felker
2018-01-01 19:52 ` Markus Wichmann
2018-01-01 22:57 ` John Reiser
2018-01-02 1:49 ` Rich Felker
2018-01-02 3:15 ` John Reiser
2018-01-02 19:49 ` Rich Felker
2018-01-02 18:24 ` a third bug in musl clone() John Reiser
2018-01-02 19:58 ` Rich Felker
2018-01-02 22:09 ` Florian Weimer
2018-01-03 2:51 ` Rich Felker
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=72c68934-4445-c83d-7bbc-004953b2f9e9@bitwagon.com \
--to=jreiser@bitwagon.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).