Nope, not objects, but at least it's partway there. This bit is about
making method calls.
We've two issues on the front end. First, we need to be able to get a
method PMC from an object, in those cases where we want to save that
for later, and second we need to call methods. So, here's how we'
[EMAIL PROTECTED]:~/parrot/languages/perl6% man memalign
POSIX_MEMALIGN(3) Linux Programmer's ManualPOSIX_MEMALIGN(3)
NAME
posix_memalign, memalign, valloc - Allocate aligned memory
SYNOPSIS
#include
int posix_memalign(void **memptr, size_t alignment, size_t size);
Looking over the code for these ops, ISTM that the stack_push and
stack_pop functions which implements them is too bloated.
How often, in practice, is the Stack_cleanup_method cleanup thing
needed?
On those occasions when it is needed, is it ever with a Num, Int, or
Str? Or is it only with PMCs
> Luke Palmer <[EMAIL PROTECTED]> wrote:
>
> > It appears JIT is entirely broken. It broke recently, as it was
> > working well for me just a couple days ago.
>
> > I'm running i686 (P3) Linux, gcc-3.2.2
>
> > I get segfaults with both imcc -Oj and parrot -j (with assemble.pl) on
> > mandel.pas
Dan Sugalski wrote:
[ zerofilled aligned memory ]
That, as much as anything, argues for an entry in platform.c to get and
return large sections of memory. I know it's reasonably doable on a lot
of platforms, just potentially differently everywhere.
BTW the zero filled memory is not that impor
