search for: pr5162

...able to live without lazy compilation (even though it noticably slows down some code), but it goes without saying that as a functional language Pure definitely needs TCO. So I can only hope that this will be fixed before the LLVM 2.7 release. Ok, so what next? Should I submit a bug report? Reopen PR5162? Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr.Graef at t-online.de, ag at muwiinfa.geschichte.uni-mainz.de WWW: http://www.musikinformatik.uni-mainz.de/ag

...zy compilation (even though it > noticably slows down some code), but it goes without saying that as a > functional language Pure definitely needs TCO. So I can only hope that > this will be fixed before the LLVM 2.7 release. > > Ok, so what next? Should I submit a bug report? Reopen PR5162? Can you prepare a standalone testcase that demonstrates the problem? See unittests/ExecutionEngine/JIT/*.cpp to get your started. Nick

On Sun, Nov 29, 2009 at 2:19 AM, Albert Graef <Dr.Graef at t-online.de> wrote: > Jon Harrop wrote: >> I've come up with the following minimal repro that segfaults on my machine: > > Jon, were you able to resolve this? > > FWIW, TOT is causing all kinds of weird segfaults related to tail calls > in my Pure interpreter, too (at least on x86-64). In my case these

Jon Harrop wrote: > I've come up with the following minimal repro that segfaults on my machine: Jon, were you able to resolve this? FWIW, TOT is causing all kinds of weird segfaults related to tail calls in my Pure interpreter, too (at least on x86-64). In my case these seem to be limited to the JIT, however (batch-compiled Pure programs via opt+llc all work fine, even with TCO), so