Hi! This is the ezmlm program. I'm managing the
perl6-compi...@perl.org mailing list.

I'm working for my owner, who can be reached
at perl6-compiler-ow...@perl.org.


Messages to you from the perl6-compiler mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.

If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the perl6-compiler mailing list,
without further notice.


I've kept a list of which messages from the perl6-compiler mailing list have 
bounced from your address.

Copies of these messages may be in the archive.

To retrieve a set of messages 123-145 (a maximum of 100 per request),
send an empty message to:
   <perl6-compiler-get.123_...@perl.org>

To receive a subject and author list for the last 100 or so messages,
send an empty message to:
   <perl6-compiler-in...@perl.org>

Here are the message numbers:

   7360

--- Enclosed is a copy of the bounce message I received.

Return-Path: <>
Received: (qmail 28270 invoked from network); 22 Aug 2011 13:48:05 -0000
Received: from x1.develooper.com (207.171.7.70)
  by x6.develooper.com with SMTP; 22 Aug 2011 13:48:05 -0000
Received: (qmail 4729 invoked by uid 225); 22 Aug 2011 13:48:04 -0000
Delivered-To: perl6-compiler-return-7360-perl6-all-poster=perl....@perl.org
Received: (qmail 4723 invoked by alias); 22 Aug 2011 13:48:04 -0000
Received: from unknown (HELO x6.develooper.com) (10.0.100.16)
  by x1.dev with SMTP; 22 Aug 2011 13:48:04 -0000
Received: by x6.develooper.com (Postfix)
        id 238D3177DE; Mon, 22 Aug 2011 06:48:04 -0700 (PDT)
Date: Mon, 22 Aug 2011 06:48:04 -0700 (PDT)
From: mailer-dae...@x6.develooper.com (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: perl6-compiler-return-7360-perl6-all-poster=perl....@perl.org
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="1EE6A17DA0.1314020884/x6.develooper.com"
Message-Id: <20110822134804.238d317...@x6.develooper.com>

This is a MIME-encapsulated message.

--1EE6A17DA0.1314020884/x6.develooper.com
Content-Description: Notification
Content-Type: text/plain; charset=us-ascii

This is the mail system at host x6.develooper.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to <postmaster>

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<perl6-all-pos...@perl.org>: host mx.develooper.com[207.171.7.76] said: 552 The
    Date in the header was too far in the past (in reply to end of DATA
    command)

--1EE6A17DA0.1314020884/x6.develooper.com
Content-Description: Delivery report
Content-Type: message/delivery-status

Reporting-MTA: dns; x6.develooper.com
X-Postfix-Queue-ID: 1EE6A17DA0
X-Postfix-Sender: rfc822; 
perl6-compiler-return-7360-perl6-all-poster=perl....@perl.org
Arrival-Date: Mon, 22 Aug 2011 06:47:53 -0700 (PDT)

Final-Recipient: rfc822; perl6-all-pos...@perl.org
Original-Recipient: rfc822;perl6-all-pos...@perl.org
Action: failed
Status: 5.0.0
Remote-MTA: dns; mx.develooper.com
Diagnostic-Code: smtp; 552 The Date in the header was too far in the past

--1EE6A17DA0.1314020884/x6.develooper.com
Content-Description: Undelivered Message
Content-Type: message/rfc822

Received: from lists-nntp.develooper.com (localhost.localdomain [127.0.0.1])
        by x6.develooper.com (Postfix) with SMTP id 1EE6A17DA0
        for <perl6-all-pos...@perl.org>; Mon, 22 Aug 2011 06:47:53 -0700 (PDT)
Received: (qmail 26215 invoked by uid 514); 22 Aug 2011 13:47:23 -0000
Mailing-List: contact perl6-compiler-h...@perl.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:perl6-compi...@perl.org>
List-Help: <mailto:perl6-compiler-h...@perl.org>
List-Unsubscribe: <mailto:perl6-compiler-unsubscr...@perl.org>
List-Subscribe: <mailto:perl6-compiler-subscr...@perl.org>
List-Id: <perl6-compiler.perl.org>
Delivered-To: mailing list perl6-compi...@perl.org
Delivered-To: moderator for perl6-compi...@perl.org
Received: (qmail 22223 invoked from network); 17 Aug 2011 14:00:44 -0000
Delivered-To: perl6-compi...@perl.org
X-Spam-Status: No, hits=-0.7 required=8.0
        
tests=DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: la.mx.develooper.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=PSUw4tIfhghanHWYj3bYRDxELdBGSSu8TnK9vsAb3EU=;
        b=SoWTyC3aFfAOXtJyXaM8o3GYR6X49/vEfHu9CDpfvCPOhD0XVgMLtlP71si1lm8d3i
         +ssmo7OhfrlHN7bPLlXBQG6Xfafm8sJorMk1d8dHySFqzlt3R0ld1//LQIuqXzbHNupt
         WV6Kqu/M+uJX808Sh64Blx764kKCrH2EIxOxw=
MIME-Version: 1.0
In-Reply-To: <1313578883.23687.140258130578...@webmail.messagingengine.com>
References: <1313578883.23687.140258130578...@webmail.messagingengine.com>
Date: Wed, 17 Aug 2011 08:23:50 -0400
Message-ID: <caepdb4ry2x7cf2gbduc1v6yg_8z3chpwpdooudlfo3v5kne...@mail.gmail.com>
Subject: Re: Some Requests from Rakudo
From: Andrew Whitworth <wknight8...@gmail.com>
To: Christoph Otto <christ...@mksig.org>
Cc: parrot-...@lists.parrot.org, perl6-compi...@perl.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Aug 17, 2011 at 7:01 AM, Christoph Otto <christ...@mksig.org> wrote:
> 1) Threading ...
> 2) Asynchronous I/O ...

These are going to be done at the same time. We're not going to have
AIO until we have at least basic threading support. What we need is a
good plan/design for a new system going forward. I had put forward
some ideas a few weeks ago, but I got a lot of good feedback and am
not so sure about some of the specifics now. Rakudo could serve as a
major driver in this area. The kind of system and the kinds of designs
we pursue could be significantly influenced by what Rakudo wants.
Also, if they have some hackers who want to get their hands dirty,
that's a big help too. The people doing the work are going to play a
major role in setting the overall direction.

> 3) sub cloning ...

I published a blog post last night addressing some of these issues,
and I've started an exploratory branch locally to try and cut down
some of the cruft of the Sub PMC. I can expand on some of my
short-term plans on IRC or in another blog post. Longer-term, the
specific goals are a lot more fuzzy. Again, guidance from the Rakudo
folks to help direct our efforts would be very welcome.

> 4) PCC ...
> 5) invocation ...

I have several ideas with respect to these items, some of which have
made it into blog posts. I've also done some comparative timings and
found that we can make some improvements to invocation performance by
adding a few new specialty PIR opcodes and avoiding the use of
fill_params and friends. The one area where I don't have a concrete
solution is a replacement for ":named :slurpy" parameters. I know NQP
makes some use of those, so we can't abandon them completely and we
can't have them be slower than the current implementation. We can chat
more about this on IRC, or I can write up more thoughts in a blog
post.

As we've said before, profiling tools will be helpful in this regard,
so we want to give that a nudge in the forward direction.

If people besides myself have ideas for any of these things, please
start making them public. They are all places where Parrot needs to
improve, but the paths we need to take to reach those improvements are
not straight-forward. The more input we have to guide decisions, the
better.

--Andrew Whitworth

--1EE6A17DA0.1314020884/x6.develooper.com--

Reply via email to