From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/1232 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Possible ARM struct stat problem. Date: Mon, 25 Jun 2012 22:50:02 -0400 Message-ID: <20120626025002.GH544@brightrain.aerifal.cx> References: <2314318.NDqLURy4mK@main.pennware.com> <20120527194319.GF163@brightrain.aerifal.cx> <4FE91B3D.2010905@barfooze.de> 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: dough.gmane.org 1340679140 18677 80.91.229.3 (26 Jun 2012 02:52:20 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 26 Jun 2012 02:52:20 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-1233-gllmg-musl=m.gmane.org@lists.openwall.com Tue Jun 26 04:52:20 2012 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 1SjLsy-00031J-1Y for gllmg-musl@plane.gmane.org; Tue, 26 Jun 2012 04:52:12 +0200 Original-Received: (qmail 3817 invoked by uid 550); 26 Jun 2012 02:52:12 -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 3809 invoked from network); 26 Jun 2012 02:52:11 -0000 Content-Disposition: inline In-Reply-To: <4FE91B3D.2010905@barfooze.de> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:1232 Archived-At: On Tue, Jun 26, 2012 at 04:15:25AM +0200, John Spencer wrote: > >I'm not entirely opposed to putting the explicit padding in there, > >since this is an arch-specific structure anyway, but I think you > >should check your compiler. The same issue might come up elsewhere and > >might not be so easy to work around. > > > please apply the explicit padding. All this would have done is hide the issue that you're using the wrong ABI (oabi instead of eabi) and make it harder to find the more-subtle resulting bugs later (mildly different calling convention and padding). Rich