[perl #28182] thr-primes.imc segfaults

# New Ticket Created by Simon Glover # Please include the string: [perl #28182] # in the subject line of all future correspondence about this issue. # http://rt.perl.org:80/rt3/Ticket/Display.html?id=28182 > examples/assembly/thr-primes.imc dies with a segfault. gdb says that it dies at:

[perl #28180] DWIM doesn't

# New Ticket Created by Simon Glover # Please include the string: [perl #28180] # in the subject line of all future correspondence about this issue. # http://rt.perl.org:80/rt3/Ticket/Display.html?id=28180 > When I try to run hello-dwim.imc from examples/assembly/, it dies with: error:im

Re: compiling hangs at core_ops_cg.c

On Fri, 2004-04-02 at 12:26, Larry Wall wrote: > Hmm, if it's getting better for you and worse for others [...] it > might well be that they've performed a miracle. Actually, they may well just be optimizing that work for memory, rather than CPU, and could be making some tragic choices with respe

Re: compiling hangs at core_ops_cg.c

K Stol <[EMAIL PROTECTED]> wrote: >> > Thanks for your tips, all! > I just had to be patient with the old computer. It compiles now (eventually) And if you want fast recompiles (w/o code changes) then install ccache. ,--[ man ccache ]-- | DESCRIPTIO

Re: compiling hangs at core_ops_cg.c

On Fri, Apr 02, 2004 at 07:02:52AM -0600, Art Haas wrote: : Newer GCC releases are _much_ better at compiling this file than older : releases. GCC-3.3 is better than GCC-3.2, GCC-3.4 is better than GCC-3.3, : but best of all is GCC-3.5, as it compiles this file in usually less than : 5 minutes and

Re: compiling hangs at core_ops_cg.c

Art Haas wrote: Jerome Quelin wrote: Dan Sugalski wrote: That'd be about three to four for the CPU you've got, and when you throw in swapping I can see the compile time for that module hitting 15-20 minutes. At least. FYI, I ran into the same problem some months ago. I had 128 Mb o

Subroutine calls

The PIR subroutine call syntax _f() expands (besides other instructions) to something like: newsub P0, .Sub, _f invokecc I've now hacked together this sequence: 1) a new opcode (in dynoplibs/myops.ops for quick testing) op pmc_const(out PMC, inlabelconst INT) { $1 = PCONST($2)->u.key;

[perl #28170] [PATCH] marginally better negative zero detection

# New Ticket Created by Andy Dougherty # Please include the string: [perl #28170] # in the subject line of all future correspondence about this issue. # http://rt.perl.org:80/rt3/Ticket/Display.html?id=28170 > ALl of the big-endian tinderboxes are currently failing t/pmc/perlnum.t test 36 (th

Re: compiling hangs at core_ops_cg.c

Jerome Quelin wrote: > Dan Sugalski wrote: >> That'd be about three to four for the CPU you've got, and when you >> throw in swapping I can see the compile time for that module hitting >> 15-20 minutes. > > At least. FYI, I ran into the same problem some months ago. I had 128 Mb > on my P4 1.3GHz

RE: Newbie Question

Thanks all, I'll give said paper a read and see if it has the details I'm digging for. I was already passively aware of the static typing issue, but wondered if there were others. kt From: Paolo Molaro [mailto:[EMAIL PROTECTED] Sent: Fri 4/2/2004 5:09 AM To: [

Re: Newbie Question

On 04/01/04 Goplat wrote: > > I read in the FAQ, vis a vis using the .NET instead of writing your own > > "The .NET VM didn't even exist when we started development, or at least we > > didn't know about it when we were working on the design. We do now, though > > it's still not suitable." [...] > T

Re: Making tail calls/invoking continuations

Piers Cawley <[EMAIL PROTECTED]> wrote: > Is there any syntactic sugar in IMCC for making a tail call? No. > Right now, AFAICT, the trick is to do: >.pcc_begin >.arg Foo >.arg bar >.pcc_call sub, P1 # Or whatever the syntax is to get > # the current continuat

Re: [PATCH] signals under x86_64

Adam Thomason sent the following bits through the ether: > No troubles here (see the palaeodictyoptera tinderbox). Is procps > up-to-date? Is NPTL causing different PIDs to show up? OK, chalk it up to dodgy Fedora in that case. Please do not apply patch. Leon -- Leon Brocard..

Re: [perl #28151] [PATCH] Compound keys for PerlHash

Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote: > I noticed that I couldn't use compound keys for setting values in a > PerlHash. > Retrieving values seems to work OK. Thanks, applied. leo

Re: Fun with nondeterministic searches

Piers Cawley <[EMAIL PROTECTED]> wrote: > Well, I ported the following Scheme code to PIR. (The PIR is appended > to this message... I've cleaned up the whole freelist handling code now and added your code as a test, which exposed one more bug: it didn't run with --gc-debug. That's fixed now too-

[NEW] Stream library

Hi all, attached is a first working development version of a Stream library. A stream is a continuous source of strings. A string can be read with the "read" method. The stream class has per design no "seek" or "tell" methods. A later version will support cloning in order to replay the content

Re: Fun with nondeterministic searches

Leopold Toetsch <[EMAIL PROTECTED]> writes: > Piers Cawley <[EMAIL PROTECTED]> wrote: > >> When you make a full continuation with clone, can't you chase up its >> continuation chain and mark its reachable continuations (and only those >> continuations) as non recyclable? (This is one of the reason

Making tail calls/invoking continuations

Is there any syntactic sugar in IMCC for making a tail call? Right now, AFAICT, the trick is to do: .pcc_begin .arg Foo .arg bar .pcc_call sub, P1 # Or whatever the syntax is to get # the current continuation .pcc_end But, looking at the PASM generated by pcc_4