mailing list of musl libc
 help / color / mirror / code / Atom feed
From: John Spencer <maillist-musl@barfooze.de>
To: musl@lists.openwall.com
Subject: Re: Possible ARM struct stat problem.
Date: Tue, 26 Jun 2012 05:12:02 +0200	[thread overview]
Message-ID: <4FE92882.1030503@barfooze.de> (raw)
In-Reply-To: <20120626025002.GH544@brightrain.aerifal.cx>

On 06/26/2012 04:50 AM, Rich Felker wrote:
> 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
>
indeed.
i'm trying to fix the toolchain by passing an explicit 
--target=arm-linux-gnueabi to configure.
since ARM toolchains appear to full of such hidden traps, i vote +1 for 
adding some assertions that the right ABI is used.



      parent reply	other threads:[~2012-06-26  3:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-27 18:35 Richard Pennington
2012-05-27 19:43 ` Rich Felker
2012-05-27 23:03   ` Szabolcs Nagy
2012-05-28 13:13   ` Richard Pennington
2012-06-26  2:15   ` John Spencer
2012-06-26  2:50     ` Rich Felker
2012-06-26  2:52       ` Richard Pennington
2012-06-26  3:01         ` Rich Felker
2012-06-26  3:12       ` John Spencer [this message]

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=4FE92882.1030503@barfooze.de \
    --to=maillist-musl@barfooze.de \
    --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).