Nattfodd <[EMAIL PROTECTED]> wrote:
> Hi,
> today is the deadline for the google summer of code projects, and it's
> time anyway for a "release" of GMC.
[ two additional remarks, rest sent in PM ]
1) docs
Some recent changes, like reversing the scavenge direction isn't yet
synced to documentati
On Sat, 3 Sep 2005, Nattfodd wrote:
> thanks for the investigation, I'll look closely to it. It was reported
> to fail on AMD64 too but we did not try setting GMC_ALIGN to 16. Also be
> warned that I am very far from an alignment master, so I may have done
> things wrong in my small hack.
At f
Andy Dougherty wrote:
On Fri, 2 Sep 2005, Nattfodd wrote:
I added in the last revision some very basic memory alignment control
(basically, headers and bodies are rounded up to the nearest multiple of
GMC_ALIGN, which has a value of 8 now but can be changed at will. As headers
were previous
On Fri, 2 Sep 2005, Nattfodd wrote:
> I added in the last revision some very basic memory alignment control
> (basically, headers and bodies are rounded up to the nearest multiple of
> GMC_ALIGN, which has a value of 8 now but can be changed at will. As headers
> were previously using 12 bytes, th
Much better on OS X now!
parrot:
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/dynclass/pyclass.t1 256 61 16.67% 6
t/dynclass/pyfunc.t 1 256 41 25.
On 9/2/05, Nattfodd <[EMAIL PROTECTED]> wrote:
>
> ...but it should be fine as
> long as you define GMC_GC_RUN (at least to see if it can run correctly
> miniparrot)...
err, it was GMC_NO_GC_RUN, of course.
Now I'll really use some sleep :)
Andy Dougherty wrote:
Overall, I wonder if it's an alignment issue, since SPARC tends to be
much more sensitve to that than x86. I haven't looked deeply at the
code at all, but do you do anything special to ensure that the blocks
of memory you are moving around maintain their aligment?
On Thu, 1 Sep 2005, Nattfodd wrote:
> Andy Dougherty wrote:
>
> > On Thu, 1 Sep 2005, Nattfodd wrote:
> >
> >
> > > today is the deadline for the google summer of code projects, and it's
> > > time
> > > anyway for a "release" of GMC.
> > > GMC is a generational garbage collector for parrot th
Andy Dougherty wrote:
On Thu, 1 Sep 2005, Nattfodd wrote:
today is the deadline for the google summer of code projects, and it's time
anyway for a "release" of GMC.
GMC is a generational garbage collector for parrot that allows copying of
objects and thus copying GC schemes.
Thanks f
On Thu, 1 Sep 2005, Nattfodd wrote:
> today is the deadline for the google summer of code projects, and it's time
> anyway for a "release" of GMC.
> GMC is a generational garbage collector for parrot that allows copying of
> objects and thus copying GC schemes.
Thanks for submitting this. I also
After svn up, realclean, configure; make:
~/research/gmc wcoleda$ make parrot
Invoking Parrot to generate runtime/parrot/include/config.fpmc --
cross your fingers
./miniparrot config_lib.pasm > runtime/parrot/include/config.fpmc
make: *** [runtime/parrot/include/config.fpmc] Error 138
Running
Will Coleda wrote:
On Aug 31, 2005, at 7:03 PM, Nattfodd wrote:
If people are willing to test real programs with it, it would really
be nice !
Thought I'd give languages/tcl a whirl, but after a fresh checkout of
the GMC branch:
% perl Configure.pl; make
perl build_tools/jit2h.pl
On Aug 31, 2005, at 7:03 PM, Nattfodd wrote:
If people are willing to test real programs with it, it would
really be nice !
Thought I'd give languages/tcl a whirl, but after a fresh checkout of
the GMC branch:
% perl Configure.pl; make
perl build_tools/jit2h.pl ppc src/jit_cpu.c
jit2h
Hi,
today is the deadline for the google summer of code projects, and it's
time anyway for a "release" of GMC.
GMC is a generational garbage collector for parrot that allows copying
of objects and thus copying GC schemes.
There are two main parts :
- The first is a new object definition (se
14 matches
Mail list logo
