Re: [gccsdk] LLVM (was: Parsing wget output)

In message <b72741df52.Jo@hobbes.bass-software.com> you wrote:

> So IMHO LLVM/Clang + EABI is a reasonable candidate as a future RISC OS
> compiler.
>
> The biggest reason for that success is the EABI choice as the alternative,
> APCS-32, would require the development of a new target (basically also the
> biggest and most trickiest work done for gcc as well). And this adds
> another reason to seriously consider adopting an EABI flavoured target,
> instead of APCS-32, for any future compiler work.
>
> If we would adopt EABI as new target, then the gcc compiler option remains
> open and would make most of our patches redundant which is always a pro,
> the less custom changes we have, the better.
>
> The question is whether there is sufficent momentum from RISC OS developer
> community to support this all.

This may be a tangential remark. Since QualComm announced it was
sponsoring the development of LuaJIT for ARM platforms I have been
wondering whether RISC OS would ever get LuaJIT. It turns out that
the LuaJIT for ARM development has been only for EABI and not
APCS-32.
--
Gavin Wraith (gavin@wra1th.plus.com)
Home page: http://www.wra1th.plus.com/

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK