From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Conformance issues to address after 0.9.12 release
Date: Tue, 13 Aug 2013 05:45:55 +0200 [thread overview]
Message-ID: <20130813034555.GF5368@port70.net> (raw)
In-Reply-To: <20130813033231.GB221@brightrain.aerifal.cx>
* Rich Felker <dalias@aerifal.cx> [2013-08-12 23:32:32 -0400]:
> Why the push/pop? Is there a reason you can't just store over top of
> the argument slot at 4(%esp) or even below the stack pointer at
> -4(%esp)? The latter would be unsafe if you ever wanted to read back
> the value since it could be clobbered asynchronously by a signal
> handler, but you don't want/need to read it back anyway.
ah ok
did not know the callee can modify those
next prev parent reply other threads:[~2013-08-13 3:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 6:34 Rich Felker
2013-07-29 16:00 ` Szabolcs Nagy
2013-07-29 21:04 ` Rich Felker
2013-07-30 2:26 ` Szabolcs Nagy
2013-08-12 19:27 ` Szabolcs Nagy
2013-08-13 3:32 ` Rich Felker
2013-08-13 3:45 ` Szabolcs Nagy [this message]
2013-08-13 4:25 ` 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=20130813034555.GF5368@port70.net \
--to=nsz@port70.net \
--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).