At 20:47 on 11/13/2002 GMT, Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 13, 2002 at 03:06:03PM -0500, Dan Sugalski wrote:
>
> > The goal is for Parrot to require a C compiler and a platform shell
> > or Make tool (either one) and that's it. We will ship with bytecode
> > files that
On Wed, Nov 13, 2002 at 03:06:03PM -0500, Dan Sugalski wrote:
> The goal is for Parrot to require a C compiler and a platform shell
> or Make tool (either one) and that's it. We will ship with bytecode
> files that have the bits needed for the build precompiled, so if the
> perl compiler's part
I'm about to do exceptions, and as such I wanted to give a quick
warning to everyone who does Odd Things. (Which would be in the JIT,
mainly :)
Because of the way exceptions are going to work, we need to make sure
that the code emitted for each individual opcode is self-contained,
relative to
At 5:16 PM +0530 11/13/02, Gopal V wrote:
If memory serves me right, Markus Laire wrote:
Miniparrot can then be used to build everything else, including full
parrot, perl6, other parrot-supported languaged, etc..
This 2nd step might be e.g. Bytecode-compiled perl6-program which is
simple eno
Daniel Grunblatt wrote:
You will see it running as fast as mops.c compiled with -O3 if you change
REDO: sub I4, I4, I3
for
REDO: dec I4
I didn't want to change the test case ;-)
But that's obviously part of a higher level optimizer.
Yes, with constant propagation the (todo) optimizer woul
On Wed, Nov 13, 2002 at 11:08:08AM +0200, Markus Laire wrote:
> On 12 Nov 2002 at 16:40, Marius Nita wrote:
>
> > Hello,
> >
> > I have a question about the Parrot FAQ. I hope it's not too
> > off-topic for this list. The FAQ mentions that "it would be nice to
> > write the Perl to Bytecode compi
You will see it running as fast as mops.c compiled with -O3 if you change
REDO: sub I4, I4, I3
for
REDO: dec I4
But that's obviously part of a higher level optimizer.
On Wednesday 13 November 2002 15:10, Leopold Toetsch wrote:
> Watch the mops ;-)
>
> leo
On Nov-13, Leopold Toetsch wrote:
> Daniel Grunblatt wrote:
>
> > On Wednesday 13 November 2002 08:06, Leopold Toetsch wrote:
> >
> >>I could localize a long outstanding bug in JIT causing 4 perl6 tests to
> >>fail.
>
> > I wonder who was the #%$# that introduced that bug . D'OH! :)
>
> Wow,
On Wednesday 13 November 2002 11:48, Leopold Toetsch wrote:
> Daniel Grunblatt wrote:
> > On Wednesday 13 November 2002 08:06, Leopold Toetsch wrote:
> >>I could localize a long outstanding bug in JIT causing 4 perl6 tests to
> >>fail.
> >
> > I wonder who was the #%$# that introduced that bug
On Wed, Nov 13, 2002 at 08:25:52AM -0800, Brent Dax wrote:
> Gopal V:
> # If memory serves me right, Markus Laire wrote:
> # > Miniparrot can then be used to build everything else, including full
> # > parrot, perl6, other parrot-supported languaged, etc..
> # >
> # > This 2nd step might be e.g. B
Gopal V:
# If memory serves me right, Markus Laire wrote:
# > Miniparrot can then be used to build everything else, including full
# > parrot, perl6, other parrot-supported languaged, etc..
# >
# > This 2nd step might be e.g. Bytecode-compiled perl6-program which is
# > simple enough to work with
Piers Cawley writes:
>
> FMTWYENTK about ":="
> Bravely declining to expand the acronym in his subject, arcardi posted a
> summary of his current understanding of the behavior of ":=", the
its "far more then what you ever need to know"
and after Damian Conway answer it becomes JEOWY
Daniel Grunblatt wrote:
> On Wednesday 13 November 2002 08:06, Leopold Toetsch wrote:
>
>>I could localize a long outstanding bug in JIT causing 4 perl6 tests to
>>fail.
> I wonder who was the #%$# that introduced that bug . D'OH! :)
Wow, Daniel, the lost son himself ;-)
So I immediately ha
On Wednesday 13 November 2002 08:06, Leopold Toetsch wrote:
> I could localize a long outstanding bug in JIT causing 4 perl6 tests to
> fail.
> When an opcode was a branch target as well as a branch source, the
> branch target got lost, causing wrong basic blocks, implying missing
> register loads
If memory serves me right, Markus Laire wrote:
> Miniparrot can then be used to build everything else, including full
> parrot, perl6, other parrot-supported languaged, etc..
>
> This 2nd step might be e.g. Bytecode-compiled perl6-program which is
> simple enough to work with miniparrot.
Please
I could localize a long outstanding bug in JIT causing 4 perl6 tests to
fail.
When an opcode was a branch target as well as a branch source, the
branch target got lost, causing wrong basic blocks, implying missing
register loads ...
All perl6 tests are now ok on JIT too.
leo
On 12 Nov 2002 at 16:40, Marius Nita wrote:
> Hello,
>
> I have a question about the Parrot FAQ. I hope it's not too
> off-topic for this list. The FAQ mentions that "it would be nice to
> write the Perl to Bytecode compiler in Perl" and that there is no
> bootstrap problem.
>
> Does this mean
The Perl 6 Summary for the week ending 20021110
Far off in distant Newark a figure, muttering something about `Leon
Brocard', shambles across a railway bridge and makes its way into a
waiting room. Time passes. After a while, a train arrives and the figure
shambles on board, takes i
18 matches
Mail list logo
