Re: Initial bignum pdd

, then everything will end up being ok. ENOTENOUGHELECTRONSTOWRITETHATNUMBERDOWNON Nicholas Clark -- ENOCFT

[Applied] Re: [Patch] Fix a warning

_arena->GC_data = mem_sys_allocate(sizeof(PMC *) * PMC_HEADERS_PER_ALLOC); > - memset(new_arena->GC_data, NULL, sizeof(PMC *) * PMC_HEADERS_PER_ALLOC); > + memset(new_arena->GC_data, 0, sizeof(PMC *) * PMC_HEADERS_PER_ALLOC); You didn't say which compiler disliked the old version.

[Applied] Re: [Patch] Add ending boilerplate

mbo on perl6-internals? Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: Extensions

and the V string, but I'm still not sure if I like this hybrid that isn't quite either. > I'm sure other people have ideas on this. Let 'em fly--the more the > merrier. Do we have a "spec" of things we like about XS (apart from typemaps), things we don't

Re: Extensions

rguments. And this is perl ("there's more than one way to do it") and IIRC "just many is left as an exercise for the reader" - I see nothing stopping anyone implementing an "alternative" system that is even better than the real thing. (why am I plugging NMS? I'm not even using them, let alone finding the tuits to help contribute) Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: 0.0.4 imminent

On Tue, Mar 05, 2002 at 09:38:37AM -0500, Bryan C. Warnock wrote: > On Tuesday 05 March 2002 05:06, Simon Cozens wrote: > > As usual, if there's anything that you think REALLY MUST HAPPEN before > > release, speak now or forever hold thy peace. > > A quick run through the docs/README/etc to make

Re: Assembler PDD

(I also found this: Content-Type: text/plain; charset="us-ascii"; format=flowed ) Here's 0,1,2,3,4 dots at the start of a line to see if it's the list software, also Bcc'ed to me somewhere else as a control [should be fairly reliable, it's exim all the way there] .. .

Re: The Big switch() in the (Blue) Sky [was: Re: Parrot is evil]

On Sun, Feb 24, 2002 at 10:01:15PM -0500, Gregor N. Purdy wrote: > Nicholas -- > > On Fri, 2002-02-22 at 19:23, Nicholas Clark wrote: > > Do you have the benchmarking code handy? > > [ie I'd like to see if what I'm thinking of comes anywhere near, on a > >

[APPLIED] Re: [PATCH] More tests for abs, inc and dec

On Sat, Mar 09, 2002 at 09:18:17PM +, Simon Glover wrote: > > The enclosed patch fixes a few of the holes in our test coverage > uncovered by Josh Wilmes Thanks, applied. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

[APPLIED] Re: [PATCH] More regex tests

On Sun, Mar 10, 2002 at 01:40:09PM -0500, Simon Glover wrote: > > Enclosed patch fixes up a few more holes in our test coverage. Thanks, applied Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

[APPLIED] Re: [PATCH] PerlString tests

On Sun, Mar 10, 2002 at 05:22:18PM -0500, Simon Glover wrote: > > More tests for the PerlString test-suite. On Sun, Mar 10, 2002 at 05:19:51PM -0500, Simon Glover wrote: > > Self-explanatory. > +output_is(

Re: [PATCH] Core.ops documentation nits

> =cut Gah. This one got fuzzed into the wrong place. > @@ -1318,7 +1315,9 @@ > > > > -=item B(out INT, in INT) > +=item B(out INT, in INT) > + > +=item B(out NUM, in NUM) > > Set $1 to the negative of $2. > &g

Re: [PATCH] Remove duplicate PerlUndef tests

> > Simon > > --- t/pmc/pmc.t.old Tue Feb 12 15:23:30 2002 > +++ t/pmc/pmc.t Tue Feb 12 15:25:07 2002 I preferred the patch in the original e-mail, because it didn't have the mangled whitespace at the line endings :-) Thanks, applied Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

[APPLIED] Re: [PATCH] Core.ops documentation nits

On Mon, Mar 11, 2002 at 05:02:45PM -0500, Simon Glover wrote: > > On Mon, 11 Mar 2002, Nicholas Clark wrote: > > > On Sat, Feb 16, 2002 at 10:32:10PM +, Simon Glover wrote: > >^ > > Should I apply the revised patch as appended? > >

Re: [bugs-parrot@netlabs.develooper.com: [netlabs #423] Fwd: Parrot segfaults on substr]

ne CVS blamelog, and then mail nastygrams at the person it says was responsible. Or just mail the coredumps :-) Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: GC and allocation controls?

h what I was thinking. If we expose the controls without some sort of "Under Construction" sign then it would preclude us from ever using a fundamentally different garbage collector later on, as it wouldn't have the same sort of controls that parrot had committed to providing. Hence I t

Re: GC and allocation controls?

I think he's right; I would like to be able to write a perl6 script that says "don't make GC stall" and still have it work when I ran it on a perl6 implementation with a different sort of GC. [and if that GC never stalled, or at least didn't have a choice of speed v

Re: Gentlemen, test your builds

.o -c encodings/utf32.c encodings/utf32.c: In function `utf32_skip_forward': encodings/utf32.c:54: warning: cast discards qualifiers from pointer target type encodings/utf32.c: In function `utf32_skip_backward': encodings/utf32.c:62: warning: cast discards qualifiers from pointer target type Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

[PATCH] 5.005_03 (was Re: New assembler ready for tasting)

ror messages don't tell you what you did wrong. This does: /usr/local/bin/perl Configure.pl Perl 5.00503 required--this is only version 5.00405, stopped at Configure.pl line 10. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/ --- Configu

[APPLIED] Re: [PATCH] Squelch PMC warnings

quot;); > + return 0; I'd not looked - I didn't realise that it was this simple. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: Important

the person responsible for Outlook... I wrote the spec for the solution ages ago, but no-one yet seems to have implemented it: http://www.ccl4.org/~nick/ahfw (so long ago that it was still called "New Technogy") Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

[Applied] Re: [DOC PATCH] Tests.pod tweakage

On Tue, Mar 19, 2002 at 10:41:10AM -0500, Simon Glover wrote: > > 1. There are tests in t/pmc as well as t/op now. > 2. Adds a comment about Parrot::Test Thanks, applied Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

[Applied] Re: [DOC PATCH] Small fix to running.pod

On Tue, Mar 19, 2002 at 10:11:06AM -0500, Simon Glover wrote: > > We can now get usage information for test_parrot without having to > grep the source. Thanks, applied. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: typedefs

h parrot is being embedded into. So I think there is good reason to lumber ourselves with prefixed names. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: Coding standards (was Re: typedefs)

selves forced to compile parrot for their platform on a C++ compiler. I'm not sure how likely the latter is. The former we need to take care of (alone with all the #ifdef __CPLUSPLUS; extern "C" { shenanigans) Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: [FIX] Re: Some weekend fun: BASIC for Parrot

e of parrot's regression tests would not necessarily be that informative about where in parrot had just caused a failure, or whether the failure was a bug in the BASIC interpreter (possibly due to a misunderstanding or unspecified bit of parrot behaviour) or to a bug in parrot] Nicholas

Re: Bugfix release?

more, we are 10x more stable than > a week ago. I think Peter's patch or a variation is in order, and I'm also > working > on a new crashme :) > > Bring on 0.0.5 Peter's made it foolproof, so Melvin is about to build a better fool? :-) Long may this arms race cont

Re: [preliminary PATCH] Parrot C Compiler Wrapper

On Sat, Mar 30, 2002 at 02:12:46AM -0800, Brent Dax wrote: > If you have a Unix box and ten spare minutes, please apply this to a > fresh checkout of Parrot, run 'make test', and tell me how well it > works. FreeBSD did not enjoy it: 0 Patch did not apply cleanly: Patching file Makefile.in usi

Re: [preliminary PATCH] Parrot C Compiler Wrapper

On Sat, Mar 30, 2002 at 04:37:54PM -0800, Brent Dax wrote: > Nicholas Clark: > # Patching file Makefile.in using Plan A... > # Hunk #1 succeeded at 112. > # Hunk #2 failed at 143. > > Weird. Line endings, perhaps. This line has appeared in Makefile.in, which doesn't s

Re: Avoiding the deadlands

gt; 'memory'; is in force) > Also, the functions that set it should probably reset it when they're > done, though I could argue against requiring that one for speed > purposes. I think I'd want benchmarks for it, though. use more 'speed'; Presumably

Re: PMC pdd's in

perl programmers are used to writing ~0 when they mean -1 and vice versa, then this follows: $ perl -e 'printf "%u\n", -4.2' 4294967292 -4, -4.0 and -4.01 all have to behave the same, otherwise DWIM fails whenever floating point results aren't quite what they seem.

Re: PMC pdd's in

On Fri, May 17, 2002 at 03:27:44PM -0400, Dan Sugalski wrote: > At 8:04 PM +0100 5/17/02, Nicholas Clark wrote: > >On Thu, May 16, 2002 at 08:37:32PM -0400, Dan Sugalski wrote: > >> Pssst. Brent. Don't tell anyone, but ~0 *is* -1... :) > > > >$ perl -le &#x

Re: Profiling PMCs

ly clean and can be inherited from? That way we could have the benefit of speed for the common case, but also let people derive from them easily. In theory, all it would need to be would be two sets of vtables, wouldn't it? One "clean" vtable that implements all calls back in vi

Re: [COMMIT] inc/dec/add ops and new PMC methods

27;ll have some untested ops in the core that will get broken without anyone realising. I'm not suggesting that we do this all the time, but it might be a good rule for any official release - for release all ops must have tests. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: hash values and comparisons of strings

scoding, or how C and hash keys are going to deal with Unicode normal forms, so there may be some flaws in the above which are obvious to anyone who does understand these things. I could also have stupid mistakes in my reasoning. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: Minimum perl version ?

e for constant(), which is enough of a reason to avoid for the general case of extension building. I'm unconvinced that 5.6 offers any features over 5.005 that we really need (5.005 introduces qr//) and it seems to me that we keep the barriers to building parrot as low as practical, to en

[PATCH] Re: Minimum perl version ?

umentation for Perl, including FAQ lists, should be found on this system using `man perl' or `perldoc perl'. If you have access to the Internet, point your browser at http://www.perl.com/, the Perl Home Page. Nicholas Clark -- Even better than the real thing:http://nms

Re: several changes committed (IO, miniparrot)

ance. hosted, or freestanding? [arrgh? were those the correct terms? the minimal one doesn't have errno.h or most of the other headers, IIRC. And wince is only the minimal one] Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: [netlabs #726] -fno-strict-aliasing (fwd)

.html?id=726 > > > > > --- Forwarded Message > > Date:Tue, 11 Jun 2002 15:21:06 +0100 > From:Nicholas Clark <[EMAIL PROTECTED]> Well, that's one solution to Warnock's dilemma :-) No, in the intervening time I've not found an answer to my original questions.

Re: multidimensional array

implementation > details are just that--details. They hide on the other side of the > wall marked "Do Not Peek Past This Point". :) or "Here Be Dragons" > I really need a room with a wraparound whiteboard... Does it really matter what shape the room is, once one has had the caps off the marker pens for long enough? :-) Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: Parrot Glossary - COW

have to actually do any copying of that 2K stack frame. The same buffer just passes from $a to $b without copying, as long as the code marked ... doesn't touch $a or $b. And if the code marked ... does alter $a or $b, the internals spot the COW flag and do the copy, as if it had happened for real at the point where $b = $a; was run. Nicholas Clark

Re: vtables and multimethod dispatch

> Not to worry. There's no trig involved. Just the > Pythagorean theorem. Unless I'm being thick, x² < y² whenever x < y for positive x and y (ie you don't need to take the square root of the hypotenuse to work out which hypotenuse is shorter. And all we're actually

Re: Adding the system stack to the root set

race. If I remember correctly (which I may not) this- because there are lots of CPU registers, it is quite likely that some contain addresses of things. Hence you can't assume that the only things that get stacked that look like addresses are from program counters and suchlike. Nicholas Clark

Re: vtables and multimethod dispatch

On Thu, Jul 11, 2002 at 10:52:31AM -0700, John Porter wrote: > > Dan Sugalski wrote: > > Nicholas Clark: > > > Unless I'm being thick, x" < y" whenever x < y for positive x > > > and y (ie you don't need to take the square root of the >

Re: Parrot contribution

if they do just write code without any form of overview documentation, then they're still going to be writing code for a long time to come, because they won't recruit many helpers. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

The quest for no compiler warnings

e the warning turned on and have noise, re-order the struct to avoid the warning, turn the warning off, or "cheat" in some way by changing what jump is (int, same but 3 more chars after it, anonymous union, bitfield being 4 ways I can think of that ought to work) ? Nicholas Clark -- Even bette

Re: [perl #823] [PATCH] put numeric comparisons in the right order

point comparison: perl5.8.0-64 -le '$a = ~0; $b = $a & ~1; printf "%x <=> %x\n", $a, $b; print $a <=> $b; {use integer; print $a <=> $b}' <=> fffe 1 1 IIRC the speed difference was hard to benchmark. However, the ability to deal

Re: [perl #823] [PATCH] put numeric comparisons in the right order

On Tue, Jul 16, 2002 at 07:42:25AM -0700, Sean O'Rourke wrote: > On Tue, 16 Jul 2002, Nicholas Clark wrote: > > > 5.8.0 does the full fun and games of integer or floating point comparison: > > > > perl5.8.0-64 -le '$a = ~0; $b = $a & ~1; printf "%x

Re: Streams vs. Descriptors

hole file - lets you read direct from a tar on an uncompressed file stored in a zip file) The latter got written so that ex::lib::zip (zip files in @INC) could cope with files stored but not compressed in zip files. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: [PATCH] .dev files.

hot.c warning about how not do addition, which anyone who is about to change things will find hard to avoid reading. If they were elsewhere, then someone confident may change the code without realising that someone else already tried what they were about to do, and hit subtle pitfalls. Nicholas

Re: [PATCH] .dev files.

V setting routines (there are a lot of variants of these), magic, recycling unused SVs, SV string comparison, sv_gets, sprintf and cloning. And that list may not be complete. I had no idea so much was in there. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: [PATCH] MANIFEST update

I seem to remember that CVS can do pre and post checkin hooks, but I'm not sure what they could do apart from reformatting (eg indenting) your code. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: PARROT QUESTIONS: Use the source, Luke

, and not in a way that implies that it'll always be > there till the end of time. Which is why I think it would be really useful to be damn clear in what functions are part of the public API, and which are private and may go away, so that anyone with a copy of grep and nm could work out

Re: pmc RECALL command for preprocessor

't look like we're going to gain very much in speed by inlining it, and I've not idea how much larger that would make the code. I suspect that the size increase will cancel out most of the speed gain. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: [PRE-RELEASE] Release of 0.0.7 tomorrow evening

n he'd reconsider. In October 2000 I believed that 5.005 maintenance *is* important for the acceptance of perl6, and I still do now: http:[EMAIL PROTECTED]/msg00977.html Nicholas Clark

Re: minitutorial on submitting patches

ve been applied, and hence which appear to be lost, forgotten and in need of conclusion. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: RFC - Hashing PMC's

. Call it id and have it return an INTVAL. INTVALs are signed. Wouldn't it be better to return an unsigned value? Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

an aside on compiling speed (was Re: PARROT QUESTIONS: Keyed access)

that was optimising perl, whereas computed goto is C.) Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: [perl #15340] [PATCH] Boolean PMC

perl6 to know whether this is a good idea, and if so whether this is the best way to implement the idea. Someone else knowledgeable will have to comment) Nicholas Clark

Re: [PATCH] usleep, sleep(num)

field of the struct timeval it's passed? I seem to remember reading somewhere that the most portable way of achieving a sub second sleep was to call select() for that period waiting on no file descriptors. Nicholas Clark

Re: [perl #15401] [PATCH] Silence warnings on isxxxx() in debug.c

if we ever pass these functions characters between 128 and 255, er I mean -128 and -1, (you see the problem?) but if we do we're being naughty. And probably getting garbage back as we fall off the beginning of the lookup table. Except on nice platforms where plain char is unsigned (ARM, PPC are the only two I know of) Nicholas Clark

Re: perl5 regexp optimiser (was Re: [perl #15425] Regex bugfix and speed-up)

On Tue, Jul 23, 2002 at 11:08:28PM +0100, Simon Cozens wrote: > [EMAIL PROTECTED] (Nicholas Clark) writes: > > Is there an easy way any regexp internals guru can suggest to patch perl5's > > regexp code to disable the optimiser? > > Benchmarking product X against delib

perl5 regexp optimiser (was Re: [perl #15425] Regex bugfix and speed-up)

st to patch perl5's regexp code to disable the optimiser? This would make it much easier to get meaningful test result comparisons between perl5 and parrot, and also give an idea of what sort of regexps in parrot will gain from future work on parrot regexp optimisers? Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: problems sending patches

m so that your messages come From: yahoo.com, then you'd have to do both of the above to get mail to go back to your yahoo account) I'm curious why Reply-To is scored so highly - I don't set any Reply-To in my messages, and I didn't think that it was normal practice. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: [COMMIT] GC Speedup

keeping. As well as also having all the housekeeping needed by whatever the other faster method for GC of partially created objects was. So this idea may all be garbage anyway. Nicholas Clark PS If you're wondering what I'm smoking, currently it's dust. [on my hi-fi. I'

Re: RFC - Hashing PMC's

er two independently constructed structures are deeply C If you want to hash by reference, then you need a string that reflects something invariant about that PMC. In perl5 terms this is stringifying a reference, such as SCALAR(0x1118f0) - it's unique to that scalar. ($^X in t

Re: [PATCH] Reduce array.pmc keyed code

>", $a) or die ... will be treated as an attempt to open the named file, where the name is "" (after warning about the use of an uninitialized value - you were running with use warnings, weren't you?) Whether 5.8's distinction between C and undefined is useful enough to justify the special case is another matter. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: we need more ops.

s integers, then floating point, then strings, then regexps, then ... But even if perl6 wants this (and I can't remember if it's been officially suggested that it might), I'm not convinced that it's something that needs a vtable entry in the low level types of every PMC. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: we need more ops.

On Sun, Jul 28, 2002 at 06:59:50PM -0700, Sean O'Rourke wrote: > On Sun, 28 Jul 2002, Nicholas Clark wrote: > > On Sat, Jul 27, 2002 at 08:07:50PM -0700, Sean O'Rourke wrote: > > > Whether plain cmp (as a vtable function or an op on PMCs) should be kept > > >

ARM Jit v2

niel. I'll start writing some real JIT ops over the next few days, although possibly only for the ops mops and life use :-) [although I strongly suspect that JITting the ops the regexps compile down to would be the first real world JIT priority. How fast would perl6 regexps be with that?] Oh, and pr

[COMMIT] missing newline in unknown option error message

alid flag ? usednick@Bagpuss [parrot02]$ After: nick@Bagpuss [parrot03]$ ./parrot -? parrot: Invalid flag ? used nick@Bagpuss [parrot03]$ Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: ARM Jit v2

On Mon, Jul 29, 2002 at 10:34:00PM -0300, Daniel Grunblatt wrote: > On Mon, 29 Jul 2002, Nicholas Clark wrote: > > > Here's a very minimal ARM jit framework. It does work (at least as far as > > passing all 10 t/op/basic.t subtests, and running mops.pbc) > > Cool,

Re: drive-by-reminder: missing JITs

n is little endian mips, so it would be interesting if one core can do both that and the big endian SGI. There are some big endian ARM development boards out there, but I don't think there are any consumer products running big endian, and I've not been "good" in being endian neutral

On JITs and regexps (was several threads)

the personal conviction that parrot > regexes can be as fast or faster than their perl equivalents, if we > put a bit of effort on optimitzation. This sounds very promising. Thanks for doing this. On Mon, Jul 29, 2002 at 10:34:00PM -0300, Daniel Grunblatt wrote: > On Mon,

Re: ARM Jit v2

On Tue, Jul 30, 2002 at 10:20:51PM +0100, Nicholas Clark wrote: > On Mon, Jul 29, 2002 at 10:34:00PM -0300, Daniel Grunblatt wrote: > > On Mon, 29 Jul 2002, Nicholas Clark wrote: > > > > > Here's a very minimal ARM jit framework. It does work (at least as far as >

Re: problems sending patches

rious why Reply-To is scored so highly - I don't set any Reply-To in > >my messages, and I didn't think that it was normal practice. > > Ask the SpamAssassin folks. ;) Oh, maybe I should have asked them the above question then. Nicholas Clark

Re: [perl #15904] Configure broken on windows 9x

t last year, and was reporting to p5p on progresses with clearing up regression test failures. I think he wasn't using the 9x command.com shell though. Nicholas Clark

Re: [perl #15922] [PATCH] jit documentatiion + tweaks

t remains > unchanged on the stack to avoid pushing it every time. Does that get you more MOPS on the same machine? We want figures! Even if they are of no real meaning. :-) Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

On writing JITs

it comes down to, are we assuming that the JIT always be run on the CPU which is is targeting? I suspect the answer ought to be "avoid the special case" and so the answer to my original question should be "no, make the JIT portable" Nicholas Clark -- Even better than the rea

Re: resize_array (PerlArray)

en inside defined). In effect, all bar the last reference are in lvalue context - only the rightmost is rvalue. $ cat ~/test/drilldown.pl $\ = "\n"; $#a = 100; print scalar(@a); $x = $a[1][0]; print scalar(@a); __END__ $ perl ~/test/drilldown.pl 101 10001 Nicholas Clark

Re: Lexical variables, scratchpads, closures, ...

er a function has to support it by looking at all the bytecode in the interpreter at any given time. Some "nasty" programmer only needs to dynamicly load a library that goes up from its scope into yours and your careful check is worthless. Nicholas Clark

Re: Lexical variables, scratchpads, closures, ...

x27;t be a really huge speed penalty. [it might actually be faster, as this way all pads *are* equal, so there doesn't need to be special case code distinguishing between scopes with lexicals and scopes without.] Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: maybe-PATCH: sub/continuation/dlsym/coroutine clean-up

= pmc_new(...); while (...) { x->vtable->init(interp, x); ... } and there's only one allocation made for the loop, but a fresh temporary each time? Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: [perl #15907] [PATCH] Make warnings configurable

it to the Configure pumpking to actually commit (maybe without the above bit)) Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

abs_i_i but no abs_i

writing out abs I$foo rather than abs I$foo, I$foo then things will go slightly faster (and I suspect on all platforms, including interpreted platforms) Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: On writing JITs

I'd have to know whether to call Parrot_jit_normal_op() or Parrot_jit_cpcf_op(), so could there be a subroutine in jit.c that I could call to make the correct decision for me? Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

right shift ops

de generators will know which would be more appropriate. Which would mean two ops. But do we really want to add another entry to the vtable? Or should we add another parameter to the bitwise_shr entry to say which sort of shift we want? Or should we just do zero fill, and leave sign ex

Re: abs_i_i but no abs_i

On Sat, Aug 03, 2002 at 11:22:16AM +0100, Nicholas Clark wrote: > How come there is abs_i_i to put the absolute value of $2 into $1, but there's > no abs_i to convert $1 to absolute? > > I can write more a efficient implementation of abs_i, because I don't need to > sto

Re: abs_i_i but no abs_i

On Sat, Aug 03, 2002 at 10:51:41AM -0400, Ken Fox wrote: > Nicholas Clark wrote: > >I can write more a efficient implementation of abs_i ... things will > >go slightly faster > > The law of diminishing returns is broken for a VM. Eventually you > reach a point where

Re: [perl #15962] [PATCH] avoid uninit warning in Configure

tml?id=15962 > > > > Not all places have COMSPEC. Thanks, applied. :-) Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: ARM Jit v2

On Fri, Aug 02, 2002 at 01:06:27AM -0300, Daniel Grunblatt wrote: > > On Thu, 1 Aug 2002, Nicholas Clark wrote: > > > Here goes. This *isn't* functional - it's the least amount of work I could > > get away with (before midnight) that gets the inner loop of mop

Re: Array vs. PerlArray

robably all of the non-aggregates?). The hard part will be > coming up with a name for it... DWIM.pmc? On Thu, Aug 08, 2002 at 04:19:03PM -0400, Dan Sugalski wrote: Because it can always be recovered from CVS if we decide that it's useful and what name it should have :-) Nicholas Clark

[PATCH] Re: [perl #16024] gt.t has 2 busy CPU loops on 5.005_03

On Tue, Aug 06, 2002 at 10:38:46PM -, Simon Glover wrote: > > On Tue, 6 Aug 2002, Nicholas Clark wrote: > > > On Tue, Aug 06, 2002 at 10:17:48PM +, Nicholas Clark wrote: > > > > > > chopn S1, 1 # Check that the contents of S1 are no longe

read-only-ness of PBC files (was Constant & opcode swap ops)

ly, and whichever section needs to be read-write can be copied to other RAM and altered there. Or that section mapped in read-write. Or that section not mapped in, but read in conventionally. If I've misunderstood the bit about in place then the rest of this message is irrelevant. Nicholas Clark

Re: [perl #16114] [PATCH] faster assembler

On Sat, Aug 10, 2002 at 07:12:52PM -0400, Dan Sugalski wrote: > At 10:49 PM + 8/10/02, Nicholas Clark (via RT) wrote: > >Appended patch makes the assembler faster. The speedup was 1.8% on on machine > >I tested on, 1.3% on another. (Cumulative time to loop round all the .pasm &

Re: [perl #16114] [PATCH] faster assembler

patch to the list, even though it will no longer apply. I'd find it a lost easier to redo the trivial cut and past by copying what you did with your patch in front of me, rather than having to actually work out how to what you did from the description. But I'm lazy :-) Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

Re: [perl #16144] [PATCH] quotematch speedup

# .constant {name} {string} >$self->{constants}{$1} = $2; > } The regexp you've changed is identical to the $str_re regexp, isn't it? In which case, does changing that section to $str_re and then changing the (global) definition for $str_re to your better version give an even bigger speedup? Nicholas Clark

Re: [perl #16144] [PATCH] quotematch speedup

On Mon, Aug 12, 2002 at 04:01:13PM +0100, Simon Cozens wrote: > [EMAIL PROTECTED] (Nicholas Clark) writes: > > Well, I find assemble.pl too slow, so I like speed. > > Good grief. Maybe someone should implement it in XS; then as well as being > fast, we'd avoid duplicating

Re: [COMMIT] GC_DEBUG, Some GC Fixes, and Remaining GC Bugs

that we still need to check for pointers in the CPU registers, because on a register rich CPU is is not impossible that something has the only pointer to an in use value still only in a CPU register. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/

[COMMIT] Re: [PATCH] Re: [perl #16024] gt.t has 2 busy CPU loops on 5.005_03

I committed the following patch. assemble.pl now doesn't take heat-death-of- the-universe to run on 5.005_03. Nicholas Clark -- Even better than the real thing:http://nms-cgi.sourceforge.net/ --- assemble.pl.origSun Aug 11 09:45:10 2002 +++ assemble.pl Mon Aug 12 21:36:50

<    1   2   3   4   5   6   7   8   9   10   >