On 10 Apr 2010, at 22:33, nicolas geoffray wrote:> OK, I know why you get that UnsatisfiedLinkError. You have made > symlinks of GNU Classpath libraries with the .so suffix. Since > you're on MacOS, you should do symlinks with the .dylib suffix (I > notice that I'm not saying that on the webpage, I'll fix that right > now).Thanks - that did it! All my tests now run just like under Linux.> I'm not sure what to do about that core__init function. I will try > to create a bigger stack to see if that changes anything or if LLVM > inifinite loops.I am rather surprised that the size of a method should have an impact on stack usage, but then I haven't looked at all at how VMKit works yet. That's my next project :-) Konrad.
On Sun, Apr 11, 2010 at 7:12 PM, Konrad Hinsen <konrad.hinsen at fastmail.net>wrote> > I'm not sure what to do about that core__init function. I will try to >> create a bigger stack to see if that changes anything or if LLVM inifinite >> loops. >> > > I am rather surprised that the size of a method should have an impact on > stack usage, but then I haven't looked at all at how VMKit works yet. That's > my next project :-) >It has no impact on VMKit. The impact is on LLVM optimization passes that do recursive calls. Cheers, Nicolas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100411/2e2c3b41/attachment.html>
On 11.04.2010, at 19:14, nicolas geoffray wrote:> On Sun, Apr 11, 2010 at 7:12 PM, Konrad Hinsen <konrad.hinsen at fastmail.net> wrote >> I am rather surprised that the size of a method should have an impact on stack usage, but then I haven't looked at all at how VMKit works yet. That's my next project :-) >> > It has no impact on VMKit. The impact is on LLVM optimization passes that do recursive calls.I see... Could those passes simply be skipped for code blocks that are too large? Ideally in LLVM, since it's LLVM that imposes the restriction? I don't know much about LLVM yet, but my first thought would be that a code handling system should be able to deal with code of any size. It may decide not to optimize unusual cases, but it certainly shouldn't crash. Konrad.