[LLVMdev] Android JIT patch

[Renato Golin]

On 11 November 2013 12:03, James Lyon <jameslyon0 at gmail.com> wrote:

>  I think __aeabi is ARM EABI not Android EABI, e.g.
> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ihi0043d/index.html
> .
>

Indeed, this is why I was surprised that Android used it with GCC.



> The problem is not that the __aeabi functions are missing on Android,
> they're defined in libgcc.a, the problem is that they don't get linked in
> unless they're referenced. I don't know how this problem is avoided on
> ARM/Linux/glibc normally, but something pulls them in there according to my
> testing.
>

Knowing how Linux avoids it would help deciding which is the best solution.
Prior art is always a good start. ;)


The way to avoid disabling setLastModificationAndAccessTime is to rewrite
> it to take a path and use utime/utimes instead (incidentally the
> setLastModificationAndAccessTime function is only used by llvm-ar). I don't
> know why it was written the way it is now; i.e. I'm not sure what systems
> have futimens but not futimes and vice-verse. I would guess that the utime
> function should be universal though. There's a HAVE_UTIME_H test in
> Config.h but it doesn't seem to be used anywhere.
>

I'd guess utime should be used. This looks like a bug in llvm-ar, though.

--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131111/43f8e6cb/attachment.html>