First of all, 'cp' is NOT always available, yet you used it in the
Makefile. I edited the Makefile to change the 'cp' to 'copy' and turned
slashes to backslashes. Then, I get a ton of errors about stuff like
this:
include\parrot\jit_struct.h(7) : error C2059: syntax error : '}'
'cl'
Dan Sugalski sent the following bits through the ether:
We should come up with an alternative for the bytecode files that
has the line number info out of band.
This is what Java bytecode does. It has an oob offset = line number
mapping. Are .pyc the same?
Leon
--
Leon
On Thu, Dec 20, 2001 at 01:44:04AM -0800, Brent Dax wrote:
First of all, 'cp' is NOT always available, yet you used it in the
Makefile.
Zapped.
--
It's much better to have people flaming in the flesh. -Al Aho
Brent --
First of all, 'cp' is NOT always available, yet you used it in the
Makefile. I edited the Makefile to change the 'cp' to 'copy' and turned
slashes to backslashes. Then, I get a ton of errors about stuff like
this:
include\parrot\jit_struct.h(7) : error C2059: syntax error
Brent --
Give it another try. I just messed with jit2h.pl to make it not
generate empty brace pairs.
Regards,
-- Gregor
/Inspiration Innovation Excellence (TM)\
Gregor N. Purdy
testparrot -j seems to take forever over this code:
end
I'm sure this shouldn't be. Anyone got any clues?
--
As in certain cults it is possible to kill a process if you know its true name.
-- Ken Thompson and Dennis M. Ritchie
On Thu, Dec 20, 2001 at 02:20:45PM +, Simon Cozens wrote:
I'm sure this shouldn't be. Anyone got any clues?
Me! The following seems to be an off-by-one error:
diff -d -u -r1.1 jit.c
--- jit.c 20 Dec 2001 01:57:01 - 1.1
+++ jit.c 20 Dec 2001 14:24:32 -
@@ -70,7
Gregor N. Purdy:
# Give it another try. I just messed with jit2h.pl to make it not
# generate empty brace pairs.
Builds beautifully now. Thanks.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
Nothing important happened today.
--George III of England's diary entry for
At 10:05 AM 12/20/2001 +, Leon Brocard wrote:
Dan Sugalski sent the following bits through the ether:
We should come up with an alternative for the bytecode files that
has the line number info out of band.
This is what Java bytecode does. It has an oob offset = line number
mapping. Are
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 a darned good place to start.
It does seem to
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 a darned good place to start.
$ ./test_parrot -j examples/assembly/mops.pbc
Illegal
On Thu, 20 Dec 2001, Michael G Schwern wrote:
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 a darned good place to start.
$
The attached patch implements a Parrot_sprintf function. It doesn't do
quite what you think--it just wraps the system sprintf. However, it
provides I and F sizes and is designed to interact with STRINGs. For
example:
FLOATVAL f;
INTVAL i;
STRING *str;
13 matches
Mail list logo
