Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 26 Jun 2012 05:12:02 +0200
From: John Spencer <>
Subject: Re: Possible ARM struct stat problem.

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
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.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.