Dan and Michael --
$ ./test_parrot -j examples/assembly/mops.pbc
Illegal instruction
That's not supposed to happen is it? Its Linux/PowerPC, so maybe it
is supposed to happen.
It's sort of supposed to happen. It shouldn't work, at least--we need
better error checking and such,
All --
$ ./test_parrot -j examples/assembly/mops.pbc
Illegal instruction
That's not supposed to happen is it? Its Linux/PowerPC, so maybe it
is supposed to happen.
It's sort of supposed to happen. It shouldn't work, at least--we need
better error checking and such, so
On Fri, 21 Dec 2001, Tom Hughes wrote:
In message [EMAIL PROTECTED]
Dan Sugalski [EMAIL PROTECTED] wrote:
To run a program with the JIT, pass test_parrot the -j flag and watch it
scream. Well, scream if you're on x86 Linux or BSD (I get a speedup on
mops.pbc of 35x) but it's
In message [EMAIL PROTECTED]
Daniel Grunblatt [EMAIL PROTECTED] wrote:
On Fri, 21 Dec 2001, Tom Hughes wrote:
I suspect it is also rather questionable to call system calls
directly rather than going via their C library veneers - that is
even more true when you come to things
Just some cleanups for consistent access to the interpreter in PMC code.
Index: classes/perlstring.pmc
===
RCS file: /home/perlcvs/parrot/classes/perlstring.pmc,v
retrieving revision 1.7
diff -u -r1.7 perlstring.pmc
---
Don't forget that (if I'm missing somthing) by the time that pbc2c.pl
work with all the ops it will be much slower than the jit.
Daniel Grunblatt.
On 21 Dec 2001, Tom Hughes wrote:
In message [EMAIL PROTECTED]
Daniel Grunblatt [EMAIL PROTECTED] wrote:
On Fri, 21 Dec 2001, Tom
On Thu, Dec 20, 2001 at 07:37:42AM -0500, Gregor N. Purdy wrote:
I see Simon already changed 'cp ...' to 'perl -MFile::Copy...'. I just
changed that to '$(PERL) -MFile::Copy...'.
NT 4.0's cmd shell does not like single quotes.
diff -r1.82 Makefile.in
22c22
platform$(O) $(CLASS_O_FILES)
Gregor's just committed a load of interesting stuff, and I have no
idea what it is. Hey, Gregor, what's going on?
--
Why waste negative entropy on comments, when you could use the same
entropy to create bugs instead?
-- Steve Elias
Whilst building on Sparc/Solaris 8
$ perl -V:archname
archname='sun4-solaris-64int-ld';
I saw the following odd message:
perl jit2h.pl i386 include/parrot/jit_struct.h
Package `Parrot::Jit' not found (did you use the incorrect case?) at jit2h.pl line 7.
Later, while testing ./test_parrot -j,
Simon --
Gregor's just committed a load of interesting stuff, and I have no
idea what it is. Hey, Gregor, what's going on?
I'm working on some cleanup to the various scriptage related to op
processing. I still have some things in mind, but (IMO) its looking
better.
I'm going to post a
All --
Here's the log from the infamous commit.
Changes to syntax of .ops files and refactoring of ops2c*.pl and
pbc2c.pl.
* Removed ops2c-prederef.pl
* (unrelated) Removed vestigial Parrot/Opcode.pm file.
* Added Parrot/OpTrans.pm, Parrot/OpTrans/C.pm (needed for old
Andy --
Whilst building on Sparc/Solaris 8
$ perl -V:archname
archname='sun4-solaris-64int-ld';
This could cause some trouble. I was expecting cpuarch-osname
(two dash-separated components only). I think we'll happily
ignore the latter two entries, though. Do you consider sun4
to be the
On Fri, 21 Dec 2001, Gregor N. Purdy wrote:
Andy --
Whilst building on Sparc/Solaris 8
$ perl -V:archname
archname='sun4-solaris-64int-ld';
This could cause some trouble. I was expecting cpuarch-osname
(two dash-separated components only). I think we'll happily
ignore the latter
On Fri, 21 Dec 2001, Gregor N. Purdy wrote:
Andy --
Whilst building on Sparc/Solaris 8
$ perl -V:archname
archname='sun4-solaris-64int-ld';
I saw the following odd message:
perl jit2h.pl i386 include/parrot/jit_struct.h
Package `Parrot::Jit' not found (did you use the
On Fri, 21 Dec 2001, Andy Dougherty wrote:
On Fri, 21 Dec 2001, Gregor N. Purdy wrote:
Andy --
Whilst building on Sparc/Solaris 8
$ perl -V:archname
archname='sun4-solaris-64int-ld';
I saw the following odd message:
perl jit2h.pl i386 include/parrot/jit_struct.h
All --
Note the package name.
Fixed.
Regards,
-- Gregor
/Inspiration Innovation Excellence (TM)\
Gregor N. Purdy [EMAIL PROTECTED]
Focus Research, Inc.
On Fri, Dec 21, 2001 at 02:59:52PM -0500, Gregor N. Purdy wrote:
* Eventually getting rid of (all?) references to the implicit args
of opfuncs (interpreter and cur_opcode). If they are implicit,
let them stay hidden. Dan is thinking this may become easier
when/if we can store
Assuming these mismatches weren't intentional, here is a patch that fixes
the mismatches between the pointer prototypes in the _vtable definition and
the function definition in the perlint, perlnum and perlstring pmc files.
David
RCS file: /cvs/public/parrot/classes/perlint.pmc,v
retrieving
18 matches
Mail list logo
