Re: Saxon for C/PHP/Python/etc

Hi O'Neil,

After hearing Tony Graham's lightening talk at the XML Summer School I
also had a look at doing this using LLVM. Like you I am using VMKit
and it sounds like we have both made about the same progress. I have
not investigated GCJ at all as it seemed to me that LLVM was the right
tool for the job.

I think you would be better seeking help on the LLVMdev mailing list
and in particular trying to attract the attention of Nicolas Geoffray
- http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-July/041438.html

I would love to hear how you get on with this, and likewise if I make
any progress I will let you know...

On 27 September 2013 11:50, Dr O'Neil Delpratt <oneil@xxxxxxxxxxxx> wrote:
> Dear XSLT community,
>
> I have recently been looking at the possbilities of making XSLT 2.0/3.0
> processor available to the C/C++ world.
> At present there seems to be a real shortage or a lack of support for
> anything greater than XSLT 1.0 (i.e libxslt, Xalan, etc).
>
> The benefits are clearly to be seen: having a fullfledged XSLT 2.0 in C
> would be great for the PHP/Python/Ruby/... communities, who currently rely
> on libxslt.
>
> So I have been looking at tools that can convert Saxon to native machine
> code. Namely LLVM and GCJ.
>
> I have had much better success using GCJ given that I managed to compile
> Saxon-HE to native machine code and actually get it to execute some
> stylesheets without any problems.
> However is GCJ the right technology to use for the task of converting Java
> code to native machine code, since it is somewhat obsolete?
>
> The LLVM project seems much more active, but I am finding it difficult to
> get anything working. I have tried the VMKit which relies on LLVM to compile
> some helloworld examples to machine code, but even that seems cumbersome.
>
> I would be grateful for feedback from anyone with experience of these
> technologies.
>
> Kind regards,
>
> O'Neil
>



-- 
Adam Retter

skype: adam.retter
tweet: adamretter
http://www.adamretter.org.uk