This existed pre-cog I did talk to apple's llvm folks who told me to figure out where the compiler creates the bad code. Oh sure... Perhaps you could take a pre cog/stack vm from 2 years back and confirm it's broken before smacking them with extras like alloca, code generation etc..
Sent from my iPhone
On Apr 3, 2012, at 12:24 PM, Eliot Miranda eliot.miranda@gmail.com wrote:
On Tue, Apr 3, 2012 at 8:29 AM, Igor Stasenko siguctua@gmail.com wrote:
ok i found why: i was using llvm compiler, not vanilla gcc.
but we should make it work on llvm eventually,
I agree, and I put some effort into this, managing to get something that starts up at -O1 (I think) but not at -O2 (or at -O0 but not at -O1). I *think* this might be a bug in llvm, because the Cogit is pretty aggressive in its use of alloca. I should try and make a report for the llvm maintainers. Either I'll find out I've made a mistake or they'll fix the bug ;) Biut finding the time is as always the issue :)
since Apple seems to be dropping support of old gcc compilers:
http://stackoverflow.com/questions/8707367/using-gcc-not-llvm-gcc-with-mac-o...
-- Best regards, Igor Stasenko.
-- best, Eliot