From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3874 Path: news.gmane.org!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: Conformance issues to address after 0.9.12 release Date: Tue, 13 Aug 2013 05:45:55 +0200 Message-ID: <20130813034555.GF5368@port70.net> References: <20130729063456.GA31564@brightrain.aerifal.cx> <20130729160046.GC25714@port70.net> <20130729210448.GG4284@brightrain.aerifal.cx> <20130730022621.GF25714@port70.net> <20130812192704.GE5368@port70.net> <20130813033231.GB221@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1376365566 31210 80.91.229.3 (13 Aug 2013 03:46:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 13 Aug 2013 03:46:06 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3878-gllmg-musl=m.gmane.org@lists.openwall.com Tue Aug 13 05:46:08 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1V95Ye-0002b1-LO for gllmg-musl@plane.gmane.org; Tue, 13 Aug 2013 05:46:08 +0200 Original-Received: (qmail 24230 invoked by uid 550); 13 Aug 2013 03:46:07 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 24222 invoked from network); 13 Aug 2013 03:46:07 -0000 Content-Disposition: inline In-Reply-To: <20130813033231.GB221@brightrain.aerifal.cx> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3874 Archived-At: * Rich Felker [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