On Apr 21, 2007, at 12:41 PM, chromatic wrote:
On Saturday 21 April 2007 04:01, Joshua Isom wrote:
I'm getting failures in t/pmc/class.t, t/pmc/exporter.t,
t/pmc/pccmethod_test.t, t/pmc/role.t, and t/pmc/smop_attribute.t and
all seem to be related to PCCMETHOD's. The failure
On Apr 21, 2007, at 8:24 PM, chromatic wrote:
Parrot_alloc_context() performs some calculations about the number of
registers used to determine how much memory to allocate:
const size_t size_n = sizeof (FLOATVAL) * n_regs_used[REGNO_NUM];
const size_t size_nip = size_n +
sizeof
Aiming to be as ANSI C compatible as possible will help to make it
build on a PDP-10, although I haven't tried it yet in an emulator. Of
course, some tweaking may be necessary, but that would only increase
portability!
On Apr 25, 2007, at 4:06 AM, Nicholas Clark wrote:
On Tue, Apr 24, 2007
I think that would be more work than truly necessary. We have an
obvious dependency on having a make that can read a generic makefile,
and a c compiler that can compile to the running architecture
successfully(cross compiling would come later). We can limit what goes
into parrot, which pmc's,
On Apr 26, 2007, at 8:28 AM, James E Keenan wrote:
Allison Randal wrote:
Nicholas Clark wrote:
I guess that the most obvious current thing that ties Parrot to the
Perl
community is that Parrot requires a copy of Perl to bootstrap, and
all the
build tools are written in Perl 5.
This is sl
On Apr 27, 2007, at 2:22 PM, Steve Peters wrote:
On Fri, Apr 27, 2007 at 09:22:22AM -0700, Steve Peters wrote:
# New Ticket Created by Steve Peters
# Please include the string: [perl #42768]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/
On Apr 29, 2007, at 12:55 PM, Allison Randal via RT wrote:
Joshua Isom (via RT) wrote:
My current svn repository uses a patch that I sent to the list about a
week ago, in which the pge tests would run with gc on if the file
DEVELOPING existed. Since I updated to over 18323,
t/compilers/pge
At the time I got this email, it was still failing when I applied the
patch, but with r18394 it's currently working again without problems.
A full make test passes with only previously failing errors.
On May 1, 2007, at 2:11 PM, chromatic wrote:
On Sunday 29 April 2007 11:18:20 Joshua
The shootouts do not generally run under the default runcore, so these
are not ideal for a standard `make test`. For most of the tests, a
quick alternative for the slow runcore can be found(for some, the input
can be generated by fasta.pir). Both are ran under JIT, so it could be
a JIT proble
On May 9, 2007, at 4:01 PM, Nicholas Clark wrote:
On Wed, May 09, 2007 at 01:06:49PM -0700, chromatic wrote:
On Wednesday 09 May 2007 12:53:57 Nicholas Clark wrote:
On Tue, May 01, 2007 at 04:41:22PM -0700, [EMAIL PROTECTED]
wrote:
+
+#define STRING_IS_NULL(s) ((s) == NULL)
+#define STRING_
On May 12, 2007, at 12:25 AM, chromatic wrote:
I agree. It may be a decent test, but it's not a test to run by
default right
now.
While I'm asking for a pony, I'd also like a way to disable the coding
standards tests for an official release tarball.
-- c
This will at least take care of t
On May 16, 2007, at 7:21 PM, James Keenan (via RT) wrote:
# New Ticket Created by James Keenan
# Please include the string: [perl #42975]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42975 >
One of the tests in t/tools/o
On May 21, 2007, at 5:56 PM, Will Coleda wrote:
I was talking to a colleague (who wishes to remain anonymous), and
s/he had a list of questions about the state of parrot that I think
should end up in the FAQ or elsewhere in the repo. I wanted to post
them here to get some discussion - I don't
On May 23, 2007, at 8:06 PM, Will Coleda wrote:
On May 23, 2007, at 1:58 AM, Joshua Isom wrote:
I confess to not grasping the point you claim is simple. As you
understand it, what is there about a register based machine, as
opposed to a stack based machine, that specifically improves the
You have to add LD_LIBRARY_PATH=.:blib/lib to your environment as in
src/dynoplibs/README(not the best place, but it's where I first found
it) to get it to work at the moment. I don't recall there always
having been an issue but it exists at the moment.
It should be noted probably that darwin
After a little prodding around, I think the problem is that the dynops
aren't build with the rpath. I don't know how "proper" the following
patch is(i.e. linux doesn't seem to have a problem so either this is
right or the other way is right), but it does the trick.
Index: config/gen/makefiles
On Jun 7, 2007, at 3:19 AM, Paul Cochrane (via RT) wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43145]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43145 >
In config/auto/jit.pm there
On Jun 18, 2007, at 4:48 PM, Andy Lester wrote:
Is there a reason we use
memcpy( dest, src, sizeof(FOO) );
instead of
*dest = *src;
The latter should be the exact same code, but be much less likely to
be screwed up.
No, they're extremely different. In the first, the data of FOO is
On Jun 21, 2007, at 12:57 PM, Mark J. Reed wrote:
On 6/21/07, Andy Lester <[EMAIL PROTECTED]> wrote:
We now have STRUCT_COPY(dest,src) and STRUCT_COPY_N(dest,src,n) for
all your struct-copying needs.
Wait! Wait! It should be src, THEN dest!
--
Mark J. Reed <[EMAIL PROTECTED]>
Are you a
On Jul 11, 2007, at 12:37 PM, Andy Dougherty wrote:
On Wed, 11 Jul 2007, Paul Cochrane wrote:
To be able to configure parrot to build with icc (the intel C
compiler) one currently needs a command line which looks like this:
perl Configure.pl --cc=icc --link=icc --ld=icc
--ccflags=" -no-gcc"
On Jul 28, 2007, at 12:54 PM, Will Coleda wrote:
Since I found myself doing this for PGE::Codestring and now for Tcl's
'__stringToList', I thought it might be a good idea to write down the
process in case anyone else finds themselves working on a similar
task.
http://www.perlfoundation.org/
On Jul 31, 2007, at 11:11 AM, Paul Cochrane (via RT) wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #44291]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44291 >
Hi all,
Attached is a pat
I'm pretty sure 0.0 always equals -0.0. I think it's part of the c
specification. Now, on OpenBSD, you can't print -0.0, as it will print
0.0 instead which is really annoying. This is with at least 3.8 but I
don't know if it's been changed since then. Anyway, to test for -0.0
instead of 0.0
On Aug 4, 2007, at 5:28 AM, Paul Cochrane wrote:
On 03/08/07, via RT Joshua Isom <[EMAIL PROTECTED]>
wrote:
# New Ticket Created by Joshua Isom
# Please include the string: [perl #44391]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/
On Aug 6, 2007, at 5:41 PM, James Keenan via RT wrote:
On Mon Aug 06 05:57:39 2007, ptc wrote:
This is the block in question in config/init/defaults.pm:
my $archname = $Config{archname};
if ($m) {
if ( $archname =~ /x86_64/ && $m eq '32' ) {
$archname =~ s/x86_64/i
On Aug 9, 2007, at 9:44 AM, Patrick R. Michaud wrote:
On Thu, Aug 09, 2007 at 07:36:11AM -0700, jerry gay wrote:
On 8/9/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
indeed. that's why
array = push item
and
$S0 = 'hello'
$S0 = say
is valid pir.
Actually, $S0 = 'hello' doesn't
On Aug 16, 2007, at 5:25 AM, Paolo Molaro wrote:
On 08/16/07 Ron Blaschke wrote:
The optimization done by the parrot jit is invalid for the x86 C
calling
convention: the area of memory containing the passed arguments
can be used as scratch space by the called function.
If you can make sure it
On Aug 20, 2007, at 7:10 PM, chromatic (via RT) wrote:
# New Ticket Created by chromatic
# Please include the string: [perl #44811]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44811 >
Test 91 fails at this PASM with th
On Aug 27, 2007, at 11:13 AM, Paul Cochrane (via RT) wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #44995]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44995 >
Hi everyone,
Another iss
As far as I know the code in question would primarily apply to Linux on
amd64. It may also apply to other systems on amd64, but I know that
particular directory structure is used with Linux. FreeBSD is not
affected(but then again, I never have gotten a 32 bit working build).
On Sep 4, 2007,
On Sep 6, 2007, at 7:52 PM, James Keenan via RT wrote:
On Fri Jun 08 06:48:12 2007, ptc wrote:
In the file config/inter/make.pm, there is the following todo item:
# FIXME this is an ugly hack
# replace the value for $(MAKE) with the actual path or we'll
end up
# with
On Sep 7, 2007, at 7:19 AM, James E Keenan wrote:
If you have gmake installed, then shouldn't
$conf->data->get('gmake_version') return a true value?
>>
>> if ( $conf->data->get('gmake_version') ) {
>> $conf->data->set( make_c => "$prog -C" );
>> }
>> else {
If so, how wou
On Sep 7, 2007, at 3:02 PM, chromatic wrote:
On Friday 07 September 2007 09:32:51 Patrick R.Michaud wrote:
Chromatic is already aware of this issue, but I thought I'd
file a ticket for it that others can hang information on.
Starting with r21103, Parrot won't build on my 64-bit platform.
It
On Sep 9, 2007, at 6:40 PM, Doug McNutt wrote:
At 21:16 +0100 9/9/07, Nicholas Clark wrote:
On Sun, Sep 09, 2007 at 10:56:20AM -0700, Jrg Plate wrote:
# http://rt.perl.org/rt3/Ticket/Display.html?id=45309 >
This patch implements the sign function for I, N, BigInt and Complex
numbers.
What sh
On Sep 12, 2007, at 6:21 PM, Will Coleda wrote:
On Sep 12, 2007, at 11:38 AM, Klaas-Jan Stol (via RT) wrote:
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #45405]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticke
On Sep 13, 2007, at 8:21 PM, Jerry Gay (via RT) wrote:
# New Ticket Created by Jerry Gay
# Please include the string: [perl #45437]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=45437 >
in r21240, ptc added a 'cover' tar
On Sep 13, 2007, at 9:00 PM, Allison Randal wrote:
Joshua Isom wrote:
And while we're add it, can we add the magic to do the same thing we
to do labels to variables as well?
What thing?
Allison
It's the little magic that turns this:
.macro foo(bar)
.local $baz:
On Sep 14, 2007, at 6:51 AM, Klaas-Jan wrote:
On Sep 14, 1:47 pm, [EMAIL PROTECTED] (Joshua Isom) wrote:
I may be slow in understanding sometimes, but I really don't know what
you mean.. :-) Could you elaborate a bit more?
Do you mean you want to get unique local variables (as the macro
I'm curious about the test coverage some of the listings. There's 100%
coverage of src/pmc/compiler.pmc but 12.5% coverage of
src/pmc/compiler.c which is created from compiler.pmc. With the
inheritence of pmc's, won't that screw with the coverage reports as
well?
But, as a side note, when I
I did get a delay email from gmail. So either gmail's servers are
screwed up and accidently resending the same email repeatedly and not
knowing it succeeded or perl.org's mail servers are screwed up and
making gmail think it needs to be delayed when it's actually sent. But
it's my first time
Oh, just pick a small section no one else bothers with. I'm setting up
again for working on complex.pmc(setting up, not working). I'm doing
amd64 jit even if it only works on FreeBSD(not enabled by default for a
reason). If you don't do anything/commit anything for a while, it's
still ok. T
For x86, you can also combine different runcores. If you try -Cj it
might run even faster. What type of program were you running to get
that slowdown? When I got the amd64 jit to the bare bones state, I got
a 10% increase in speed. If Lua's parrot implementation allows you to
turn the sourc
-Werror -Wdeclaration-after-statement
Should work according to the manpage. But just one little problem.
src/string.c
In file included from src/string.c:26:
src/string_private_cstring.h:21: warning: size of 'parrot_cstrings' is
7560 bytes
*** Error code 1
So we'd have to change some things a
It doesn't work completely with FreeBSD's make it seems. Building
'parrot' works just fine, dynpmc stuff fails with this.
g++ -o ./parrot src/main.o blib/lib/libparrot.a -lpthread -lm
-L/usr/local/lib -licuuc -licudata -lpthread -lm -lm -lcrypt -lutil
-pthread -lreadline -Wl,-E -L/usr/l
On Oct 1, 2007, at 12:45 PM, jerry gay wrote:
On 10/1/07, Paul Cochrane via RT
<[EMAIL PROTECTED]> wrote:
src/exceptions.c has a todo comment in it:
* XXX TODO get rid of all the internal_exceptions or call them
* with an interpreter arg
The fact that we can't completely get rid o
On Oct 12, 2007, at 7:33 PM, Paul Cochrane (via RT) wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #46389]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=46389 >
In src/dynpmc/gdbmhash.c t
On Oct 13, 2007, at 7:20 AM, Ron Blaschke wrote:
Attached patch should fix computed goto on Solaris with the Sun C
compiler.
All tests successful (7 subtests UNEXPECTEDLY SUCCEEDED), 11 tests and
621 subtests skipped.
Passed TODO Stat Wstat TODOs Pass List of Passed
It seems as though the first line seems to have caught my eye.
In most languages, ~ is used for bitwise not, and not bitwise xor which
is given ^. Parrot seems to do things a tad differently. An analysis
of the generated pir shows how parrot treats it now.
.sub main
$I0 = 5
On Oct 20, 2007, at 2:33 PM, Paul Cochrane via RT wrote:
The ctags program is now detected at configuration time (this program
sometimes has different names on different systems) and now 'make tags'
should work out of the box for all the variations that I'm aware of
(namely ctags, exuberant-cta
On Oct 23, 2007, at 5:45 PM, Allison Randal wrote:
Klaas-Jan Stol wrote:
Hi, attached a document describing the current macro layer of IMCC.
On the proposed modifications to macros, I have reservations on the
automatic munging of .local variable names. Macros are simple
parameterized subst
On Oct 25, 2007, at 4:35 PM, Paul Cochrane (via RT) wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #46927]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=46927 >
The attached patch removes
Did you test the exec runcore? I don't think any of that code is used
outside of the exec runcore so you aren't actually testing that code.
Also, I'm not sure the exec runcore even works. I haven't heard of it
working in quite some time.
On Nov 8, 2007, at 3:21 PM, Paul Cochrane (via RT) wr
On Nov 9, 2007, at 8:08 PM, James Keenan (via RT) wrote:
# New Ticket Created by James Keenan
# Please include the string: [perl #47313]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47313 >
The description for Parrot con
On Nov 9, 2007, at 2:24 AM, Paul Cochrane wrote:
On 09/11/2007, Joshua Isom <[EMAIL PROTECTED]> wrote:
Did you test the exec runcore? I don't think any of that code is used
outside of the exec runcore so you aren't actually testing that code.
I'll have a go at tes
On Nov 10, 2007, at 7:42 AM, James Keenan via RT wrote:
On Fri Nov 09 23:31:56 2007, [EMAIL PROTECTED] wrote:
It in no way refers to architecture actually. It refers to the
calling
convention on an architecture(dependent upon implementation). The x86
method is by pushing arguments onto the
On Nov 13, 2007, at 9:06 PM, James Keenan via RT wrote:
On Sun Nov 11 22:29:21 2007, ptc wrote:
My next guess now is that the -std=c89 gcc compiler option doesn't
play nicely with your system headers. I've removed the compiler flag
in r22809, see how you go.
Paul
It did. Now Darwin is
On Nov 14, 2007, at 1:35 PM, Andy Dougherty wrote:
I'm forwarding a message I got about the f == 0.0 warnings.
--
Andy Dougherty [EMAIL PROTECTED]
-- Forwarded message --
Date: Wed, 14 Nov 2007 10:38:10 -0500
From: Jeffrey Kegler <[EMAIL PROTECTED]>
To: Andy D
Try running Configure.pl with --execcapable=0 and you'll probably get
further through. Probably need a config hint somewhere.
On Nov 21, 2007, at 8:17 AM, Simon Dassow (via RT) wrote:
# New Ticket Created by Simon Dassow
# Please include the string: [perl #47666]
# in the subject line of al
How can you know what opcodes a dynamically loaded library provides at
compile time? If there's no other method than interp, then you'll have
to use interp to find out what's valid and what's not, without
redesigning how dynops are handled.
On Nov 27, 2007, at 1:15 PM, [EMAIL PROTECTED] wrote
On Nov 29, 2007, at 10:13 PM, Patrick R. Michaud wrote:
Also, in case it matters, I'm on x86 (32-bit) for this.
Pm
Does it still occur after `ccache -C`? Since ccache uses md5, there's
always the possibility you inadvertently discovered a collision in md5.
Might want to back up ~/.ccac
On Dec 10, 2007, at 10:59 AM, Klaas-Jan Stol wrote:
In order to draw attention to this point, I changed the subject.
Is there anybody who thinks the removal from PIR of $-less registers
("absolute" or PASM registers) should not be done?
kjs
Parrot provides a calling convention, but does no
What does atan2(0, 0) generate on tru64?
On Jan 5, 2008, at 7:51 PM, Jarkko Hietaniemi wrote:
--- src/pmc/complex.pmc.dist2008-01-06 00:48:21.0 +0200
+++ src/pmc/complex.pmc 2008-01-06 02:53:34.0 +0200
@@ -1180,7 +1180,10 @@
im = 0.0;
RE(d) = log(sqrt(
On Jan 12, 2008, at 9:42 AM, James Keenan (via RT) wrote:
# New Ticket Created by James Keenan
# Please include the string: [perl #49668]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49668 >
Test file t/op/jit.t currentl
101 - 163 of 163 matches
Mail list logo
