[Mono-dev] Building Mono on Linux/Alpha

Zoltan Varga vargaz at gmail.com
Tue Aug 29 06:59:23 EDT 2006


  The best approach, as I said previously, is to make sure all the tests (except
perhaps the pinvoke/marshalling tests) run under mono/tests. Since these tests
are much simpler than mcs, it is much easier to track down the
possible problems.


On 8/28/06, Sergey Tikhonov <tsv at solvo.ru> wrote:
> Zoltan Varga wrote:
> >                                      Hi,
> >
> >  Do you mean all tests pass inside mono/tests as well ?
> Well. :) Not all of them. I downloaded binaries for regression tests
> from the site and
> played with them. I haven't tested all of them, but the ones I tried worked.
> Ok, I guess I am trying to get it working too fast. :) btw, I've just
> almost got mcs.exe
> telling that I supplied "no files" (found stupid bug in opcode
> generation), but it got into "format problem"
> and thrown an exception.
> > As for get_vcall_slot_addr, the amd64 version is complex because the
> > amd64
> > backend generates many types of call sequences. It needs to handle the
> > machine code generated for the CALL_REG and CALL_MEMBASE opcodes.
> Ok. Alpha does function call only to an address loaded into a register,
> so I guess it might be
> really just one case for alpha.
> > As for string.format (), it is a pretty complex method, try looking at
> > its source code
> > and convert it into a self contained testcase, then try to simplify it
> > until you find
> > the root of the problem.
> Ok, I will. I just hoped that there were such test cases. :)
> Thank you,
> Sergey.
> tsv at solvo.ru
> Solvo Ltd.

More information about the Mono-devel-list mailing list