Re: [Gcc4cli-devel] SPEC2000: 176.gcc partially working

[Erven R. <erv...@in...>]

Hi Simone,

I believe you are reading this. And I imagine you have a working installation of 
ILDJIT. If we send you a CIL binary, could you give it a quick try?

David: you can try a genuine .NET on Windows machines (rdesktop meaban).

Thanks for all this!

--
Erven.


Le 18/05/2011 18:06, David Yuste a écrit :
> At this point*, 176.gcc is partially working.
>
>    It builds to CIL (cli-be), and then to native via gcil (cli-fe). The gcil-binary runs without problem, but there are small differences in the output of the program regarding the native-binary output. I will try to find out why.
>
>    Most of the efforts to make it run have been to to implement varadic arguments in gcil. Ironically, the CIL version crashes in mono due to variadic arguments. If somebody has access to a .NET environment, it would help getting feedback about this problem (I can just try with Mono).
>
> *In order to get these results you must:
>
> - Apply the attached patch. It disables some features that are not working in gcc4cli, also it fixes some actual bugs.
> - Use the last version of cli-be (remember to get into gcc-be:gcc/libstd, and make&&make install). Required in order to use new libraries in stdlib, and some fixed prototypes
> - Use the last version of cli-fe. Required to compile varadic argument functions.
> - Use the last version of cil-binutils (apply the *last* patch in "Mono.Cecil: Fixing wrong prototypes at link time"). Required, because many prototypes are fixed at linktime.
> - Build using the following flags:
>    CFLAGS+=-fno-tree-vectorize -DGCC4CLI -D__linux__ -DUSG
>    LDFLAGS+=-lm -lstd mismatch
>
>
> David Yuste
>