From: Andrew Haley <aph@redhat.com>
To: Jeff Law <law@redhat.com>, Armin Rigo <arigo@tunes.org>,
David Malcolm <dmalcolm@redhat.com>
Cc: Basile Starynkevitch <basile@starynkevitch.net>,
jit@gcc.gnu.org, GCC Development <gcc@gcc.gnu.org>
Subject: Re: GCC/JIT and precise garbage collection support?
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <55A15E39.7000906@redhat.com> (raw)
In-Reply-To: <55A01062.8000301@redhat.com>
On 07/10/2015 07:35 PM, Jeff Law wrote:
> I wonder how much overlap there is between this need and what we're
> going to need to do for resumable functions which are being discussed in
> the ISO C++ standards meetings.
A considerable amount, I'll be bound.
Andrew.
next prev parent reply other threads:[~2015-07-11 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 Basile Starynkevitch
2015-01-01 0:00 ` Andrew Haley
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Armin Rigo
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Armin Rigo
2015-01-01 0:00 ` Jeff Law
2015-01-01 0:00 ` Andrew Haley [this message]
2015-01-01 0:00 ` Trevor Saunders
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55A15E39.7000906@redhat.com \
--to=aph@redhat.com \
--cc=arigo@tunes.org \
--cc=basile@starynkevitch.net \
--cc=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jit@gcc.gnu.org \
--cc=law@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).