Svn head was broken for a big part of the day during a brain dead commit I did. Please try again.
On Mon, Feb 16, 2009 at 10:45 PM, mobbe <peter.mob...@gmail.com> wrote: > > Nope...same results with a mscorlib.dll from the 1.0 folder. It gets stuck > in > the mono_local_regalloc method on the assert checking for ins->sreg != > -1... Exactly the same message as before. It is trying to compile the > Equals > method > > The inst op code is 633 and both sreg1 and sreg2 is -1.. . > > I am running the system with build 125709 and compiling the mscorlib.dll > from the 1.0 folder... > > > > > mobbe wrote: > > > > I am indeed trying to compile a 2.0 version of the mscorlib. I will grab > > the 1.0 version instead and see if I have better luck with that one...if > I > > can get that to work then I will migrate to use the code from SVN and try > > with the 2.0 profile. > > > > Thanks, > > > > > > Zoltan Varga wrote: > >> > >> Hi, > >> > >> You might be trying to use full-aot with the 2.0 profile. Currently, > >> only the 1.0 mscorlib can > >> be full-aot-ed, altough 2.0 should work when using mono SVN. > >> > >> Zoltan > >> > >> On Mon, Feb 16, 2009 at 3:48 PM, mobbe <peter.mob...@gmail.com> wrote: > >>> > >>> I compiled the Mono framework (the unmanaged pieces) so that I could > run > >>> it > >>> on my iPhone. I was successful in doing that and thought that I would > >>> try to > >>> do AOT on the iPhone...transfer the temporary asm output to my Mac to > >>> assemble and link it and from there keep going... however when > >>> performing > >>> the AOT compilation of mscorlib.dll Mono hit another assert... > something > >>> with inst->sreg1 being negative 1 (-1) (Don't remember right now what > >>> funtion it stopped in..will have to supply that information when I get > >>> to my > >>> Mac later tonight). > >>> > >>> If I commented out the assert it went on a bit further but stopped on a > >>> another assert when trying to emit the op-code saying that it was > >>> expecting > >>> 0 bytes for the op-code ld_loadmembase but got 4... > >>> > >>> Anyone out there have an ideas of where I should be looking next in > >>> order to > >>> try to solve this? It seems like the instruction set it is using for > ARM > >>> doesn't match the source codes assumptions. I am sure that I am doing > >>> something wrong but don't know where to begin to look for the issue. > >>> Maybe > >>> someone out there has a cpu-arm.h file that they know works that I can > >>> compare with mine? Are there any other generated files regarding the > >>> instruction set that I should double check? > >>> > >>> Thanks for your help in advance. > >>> > >>> > >>> > >>> Hi, > >>> > >>> full-aot currently only works on amd64/arm. > >>> > >>> Zoltan > >>> > >>> > >>> -- > >>> View this message in context: > >>> > http://www.nabble.com/On-what-platform%7Ccpu-arch%7Cmono-version-does-full-AOT-actually-work--tp21988583p22038601.html > >>> Sent from the Mono - Dev mailing list archive at Nabble.com. > >>> > >>> _______________________________________________ > >>> Mono-devel-list mailing list > >>> Mono-devel-list@lists.ximian.com > >>> http://lists.ximian.com/mailman/listinfo/mono-devel-list > >>> > >> _______________________________________________ > >> Mono-devel-list mailing list > >> Mono-devel-list@lists.ximian.com > >> http://lists.ximian.com/mailman/listinfo/mono-devel-list > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/On-what-platform%7Ccpu-arch%7Cmono-version-does-full-AOT-actually-work--tp21988583p22049003.html > Sent from the Mono - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list >
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list