As a more concrete demonstration of what I'm talking about, here's an
implementiation of the easy part: the pinning and releasing macros.
(UNPIN would probably be better than RELEASE, huh?) It's a naive
implementation with a low fixed limit on the max number of pinned
objects (10), but at least it'
Pardon me for reopening a can of particularly slimy worms, but are we
sure we want to require all architecture/os/compiler combinations to
be able to scan all hardware registers for live pointers? This is
looking more and more problematic. For example, IA64 is kind of
similar to Parrot itself: it h
On Dec-18, Bruce Gray wrote:
> # New Ticket Created by Bruce Gray
> # Please include the string: [perl #19232]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=19232 >
>
>
> In parrot.h (revision 1.45 2002-08-07), macros
On Dec-18, Bruce Gray wrote:
> # New Ticket Created by Bruce Gray
> # Please include the string: [perl #19230]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=19230 >
>
>
> The 'clean' target in the classes makefile is o
On Dec-18, Bruce Gray wrote:
> # New Ticket Created by Bruce Gray
> # Please include the string: [perl #19229]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=19229 >
>
>
> The JIT config test is not cleaning up after it
On Dec-18, Bruce Gray wrote:
> # New Ticket Created by Bruce Gray
> # Please include the string: [perl #19227]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=19227 >
>
>
> In headers.c version 1.18, the code initializin
# New Ticket Created by Bruce Gray
# Please include the string: [perl #19232]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19232 >
In parrot.h (revision 1.45 2002-08-07), macros were defined
to eliminate warnings during
# New Ticket Created by Bruce Gray
# Please include the string: [perl #19230]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19230 >
The 'clean' target in the classes makefile is only removing
'default.h'; it should remove
# New Ticket Created by Bruce Gray
# Please include the string: [perl #19229]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19229 >
The JIT config test is not cleaning up after itself, causing
sporadic failures of the nex
# New Ticket Created by Bruce Gray
# Please include the string: [perl #19227]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19227 >
In headers.c version 1.18, the code initializing
interpreter->arena_base->extra_buffer_he
On Tue, Dec 17, 2002 at 09:40:26AM +0100, Leopold Toetsch wrote:
> Did I already say 'dubious'?
> All failing tests are floatingpoint, all use the fp_eq macro (though a
> lot more tests use this macro and don't fail). But that's all. No common
> schme beyond above, why tests fail.
>
> Could you
speaking of compiling directly to pbc, parrotbyte.pod says that number
constants should be encoded as FLOATVALs, which is a system dependant
careteristic, shouldn't there be a specified format for floats? ie
either ieee single/double float or, preferably, the number segment
specifies how bytes are
I also have a C++ compiler under development that uses flex + btyacc +
TreeCC that I can send on request. I must say that TreeCC is an extremely
nice system and one I highly recommend.
- Original Message -
From: "Gopal V" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December
Leopold Toetsch:
# In perl.cvs.parrot, you wrote:
# > -S = Parrot_sprintf_c(interpreter, "== %#x\n", ival);
#
# > +S = Parrot_sprintf_c(interpreter, "== %#vx\n", ival);
#
# I don't understand why this is changed only here, there are
# many more tests, where an C is printed with "%d"
If memory serves me right, K Stol wrote:
> I'm thinking of a compiler for Tcl which produces Parrot Assembly code,
> but the source language (which will be compiled) is not definite yet.
Instead of generating Parrot assembly, you might find it easier to
generate imcc code which is a simplified
On Tue, 17 Dec 2002, K Stol wrote:
> After doing some reading about Parrot, I got very interested. I'd like to
> write some kind of compiler for my Bacherlor's in Computer Science. I'm
> thinking of a compiler for Tcl which produces Parrot Assembly code, but
> the source language (which will be com
On Mon, Dec 16, 2002 at 06:57:40PM -0500, Dan Sugalski wrote:
> Folks,
>
> Just a reminder--our minimum requirements for build, at the moment,
> is an ANSI89 compliant C compiler (Hosted version, I think--whatever
> has a full set of headers) and perl 5.005_03. At some point we may
> raise the
Hi there,
After doing some reading about Parrot, I got very interested. I'd like to write some
kind of compiler for my Bacherlor's in Computer Science. I'm thinking of a compiler
for Tcl which produces Parrot Assembly code, but the source language (which will be
compiled) is not definite yet.
Andy Dougherty (via RT) wrote:
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #19188]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19188 >
t/pmc/pmc...# Failed test (t/pmc/pmc.t a
In perl.cvs.parrot, you wrote:
> -S = Parrot_sprintf_c(interpreter, "== %#x\n", ival);
> +S = Parrot_sprintf_c(interpreter, "== %#vx\n", ival);
I don't understand why this is changed only here, there are many more
tests, where an C is printed with "%d" format.
leo
On AIX 4.3.3 with IBM C 5.0.2 I get the following:
t/op/number.ok 9/35# Failed test (t/op/number.t at line 278)
t/op/number.NOK 10# got: '5.00
# -0.00
# 2.00
# -1.00
# 1.00
# -2.00
# '
# expected: '5.00
# 0.00
# 2.00
# -1.00
The RT System itself (via RT) wrote:
# New Ticket Created by The RT System itself
# Please include the string: [perl #19192]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19192 >
I can build parrot fine on my FreeBSD box
22 matches
Mail list logo
