On Fri Jul 11 14:00:12 2008, cotto wrote:
On Fri Jul 11 05:29:20 2008, coke wrote:
Belatedly add Moritz's response to the ticket.
A fix for this bug was committed in r29289 which looks like it will
resolve this issue. If that's the case, this ticket can be closed.
Since there haven't
/exec_cpu.c
src/jit/i386/core.jit: In function 'Parrot_eq_n_n_ic_exec':
src/jit/i386/core.jit:1031: error: 'DO' undeclared (first use in this function)
src/jit/i386/core.jit:1031: error: (Each undeclared identifier is
reported only once
src/jit/i386/core.jit:1031: error: for each function it appears in.)
src
: error: expected ';' before '{' token
src/jit/i386/core.jit: In function 'Parrot_ne_n_n_ic_exec':
src/jit/i386/core.jit:1031: error: 'DO' undeclared (first use in this
function)
src/jit/i386/core.jit:1031: error: expected ';' before '{' token
src/jit/i386/core.jit:1031: error: expected
[EMAIL PROTECTED]
Date: July 11, 2008 5:33:03 EDT
To: [EMAIL PROTECTED]
Subject: src/jit/i386/core.jit:1031: error: ?DO? undeclared
Hi,
I am using Fedora 8
Linux 2.6.23.1-42.fc8 #1 SMP Tue Oct 30 13:55:12 EDT 2007 i686 i686
i386 GNU/Linux
gcc version 4.1.2 20070925 (Red Hat 4.1.2-33
src/exec_cpu.c
src/jit/i386/core.jit: In function 'Parrot_eq_n_n_ic_exec':
src/jit/i386/core.jit:1031: error: 'DO' undeclared (first use in
this function)
Looks like it was just a DO/do typo, but the file has been changed
before I can try to do some test.
--
Salu2
Looks like it was just a DO/do typo, but the file has been changed
before I can try to do some test.
No, it was a bad diagnostic from svn, my change has been commited.
--
Salu2
Belatedly add Moritz's response to the ticket.
--
Will Coke Coleda
-- Forwarded message --
From: Moritz Lenz [EMAIL PROTECTED]
Date: Fri, Jul 11, 2008 at 6:00 AM
Subject: Re: src/jit/i386/core.jit:1031: error: 'DO' undeclared
To: tuxdna [EMAIL PROTECTED], Perl 6 Internals [EMAIL
On Fri Jul 11 05:29:20 2008, coke wrote:
Belatedly add Moritz's response to the ticket.
A fix for this bug was committed in r29289 which looks like it will
resolve this issue. If that's the case, this ticket can be closed.
