Re: [perl #50684] String Failures with -O2 (GCC 4.1.3, 32-bit x86 Linux)

2008-02-11 Thread Peter Gibbs
- Original Message - From: "chromatic (via RT)" <[EMAIL PROTECTED]> Sent: Saturday, February 09, 2008 11:29 PM Subject: [perl #50684] String Failures with -O2 (GCC 4.1.3, 32-bit x86 Linux) I recompiled Parrot with the -march and -O2 flags, to see what kind of speed boosts we get from

Parrot Bug Summary

2008-02-11 Thread Parrot Bug Summary
Parrot Bug Summary http://rt.perl.org/rt3/NoAuth/parrot/Overview.html Generated at Mon Feb 11 14:01:06 2008 GMT --- * Numbers * New Issues * Overview of Open Issues * Ticket Status By Version * Requestors with m

Re: [perl #50492] AutoReply: [PATCH][lolcode] Allow arguments to functions. Pass parameters to the appropriate functions at runtime.

2008-02-11 Thread Stephen Weeks
Not long ago, Stuart Jansen via RT proclaimed... > I'm really glad to see you're still working on this, but I don't think > this patch is ready to be merged yet. You've raised several points. Attached is a modified patch that addresses most of them. The largest problem with this patch is that it

Problem with lexical scoping

2008-02-11 Thread Andrew Parker
Hi all, I was checking a couple of things in the compiler that I wrote and put together a simple program: let x = 1 in let x = x + 1 in x which ends up being pretty much equivalent to the perl5: my $x = 1; { my $x = $x + 1; print "$x\n"; } The generated code doesn't work however. The prob

Problem with lexical scoping

2008-02-11 Thread Bob Rogers
From: Andrew Parker <[EMAIL PROTECTED]> Date: Mon, 11 Feb 2008 22:27:27 +0100 Hi all, I was checking a couple of things in the compiler that I wrote and put together a simple program: let x = 1 in let x = x + 1 in x which ends up being pretty much equivalent to the perl5:

Re: [svn:parrot] r25656 - in trunk: include/parrot src tools/build

2008-02-11 Thread chromatic
On Monday 11 February 2008 15:41:42 [EMAIL PROTECTED] wrote: > Log: > Added Parrot_assert() as a true assert wrapper around Parrot_confess(), > because splint needs to operate on a function to understand the assert() > semantics, not a macro How do we get the assert() semantics where it gets comp

Quick config/auto/pack.pm Question

2008-02-11 Thread Ron Blaschke
I noticed the following in pack.pm. sub _set_ptrconst { my ($conf, $ptrsize, $intsize, $longsize) = @_; if ( $intsize == $ptrsize ) { $conf->data->set( ptrconst => "u" ); } elsif ( $longsize == $ptrsize ) { $conf->data->set( ptrconst => "ul" ); } else {

[perl #50708] segfault in pbc_merge

2008-02-11 Thread via RT
# New Ticket Created by Ryan Voots # Please include the string: [perl #50708] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=50708 > When calling pbc_merge outside of the parrot root I encountered a segfault because pbc_mer

Re: Quick config/auto/pack.pm Question

2008-02-11 Thread James E Keenan
Ron Blaschke wrote: "l" is documented as: l A signed long (32-bit) value. I'm not expert in this, so let me ask: Where is this documented other than 'perldoc -f pack'? kid51 (... who refactored the code cited into subroutines but didn't come up with it in the first place.)