On 2/27/13 8:57 PM, Jason Detring wrote:
> On 2/27/13, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
>> On 2/27/13 4:56 PM, Jason Detring wrote:
>>> On 2/27/13, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
>>>> Can you send xfs.ko's from both native & cross-compiles? Need debugging
>>>> info in the binaries (nonstripped)
>>> I don't have a native build, sorry :-( I can put one together if
>>> necessary, but it will be quite a while on the Pi.
>> Yah I found that out ;) You could just make M=fs/xfs though?
> Done. These are also on the site at
> The directory containing cross-compiled modules has been renamed
> xfs-modules-cross/ and the new natively built modules are beneath the
> xfs-modules-native/ directory.
re-cc'ing xfs list
So I used pahole to look at all structs, objdump -d to disassemble,
and md5sum'd the results to see what's different.
pi@raspberrypi ~ $ md5sum cross/*.dis cross/*.pahole native/*.dis
so all structures look identical, good - but:
while disassembly of these two modules match:
do you see the problem w/ the cross-compiled xfs-O1-g.ko as well?
the others differ:
The diff of the disassembly of the others is huge, hard to
know where to start just yet. Need an objdump mode that only
shows function-relative addresses or something to cut down
on the noise.
> Slackware ARM (-current) also uses GCC 4.7.2 as its native compiler.
> The test modules built with it at -O2 are failing to read the
> ruby/1.9.1/ directory as well. I don't know if that's fortunate (my
> homebrew compilers are just as good or bad as the distro's?) or
> unfortunate (I still have the problem and now I am diverging from your
> native RPi results that worked).
> Is there maybe a memory or I/O tunable in the kernel .config that I've