Re: Using imcc as JIT optimizer
Leopold Toetsch wrote: Phil Hassey wrote: But with a processor with 16 registers (do such things exist?). Parrot would be overflowing registers that it could have been using in the JIT. RISC processor have a lot of them. But before there are unused processor registers, we will allocate P and S registers too. When a CPU has more then 4*32 free registers, we will look again. Like IA64? AFAIK it has 128 integer registers and 128 fp registers...
Re: [RFC] Perl Operator List, TAKE 6
Michael Lazzaro wrote: ~ - force to string context ~ ~= - string concat ARG. When did this get chosen? ~ has to be absolutly the most difficult letter to type on the intire keyboard along with ^ and , because they are also used as a prefix to make û, ü, õ, ã, ñ etc. Thus a standalone ~ must be made with a AltGr+^ followed by a space.
Re: [netlabs #482] New Tickets now come to p6i
could the http://bugs6.perl.org/rt2/Ticket/Display.html?id=XX link be posted in the messages? Robert wrote: Ok - New tickets created in the parrot queue on bugs6.perl.org are now automagically sent to p6i. You can just reply to them and the right thing will happen -- the messages will get tracked. Just keep the [netlabs #foo] string in the header. If the tickets don't show up immediately after you've created them, it's probably because they've been sent to moderation. -R (finally making all the pieces happy) -- Dennis
Re: How do we clean up?
Wizard wrote: What command can we agree on to leave only the files listed in MANIFEST and no other files? It used to be that 'distclean' did that, but no more. Just from experience, make clean should remove any files that make created, and I believe that make realclean should remove everything that wasn't there after unpacking/checkout. Given that, perhaps for our purposes, make realclean should remove all of the files not listed in MANIFEST? Very bad idea... realclean should remove all files which can be generated. Grant M.
