From: David Malcolm <dmalcolm@redhat.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: jit@gcc.gnu.org
Subject: Re: Faster JIT compilation
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <1445263982.3998.16.camel@surprise> (raw)
In-Reply-To: <CACXZuxf0AxA+jUCEQcrHmQyQBYPGzMam6=B2JJCw6ZWnWHy+bw@mail.gmail.com>
On Sun, 2015-10-04 at 20:03 +0100, Dibyendu Majumdar wrote:
> Hi Dave
>
> I was wondering if any progress has been made on removing the external
> process calls and improving the speed of JIT compilation.
I committed the first part of this (to trunk, for gcc 6) a while back,
which embeds the driver into libgccjit, saving one external process
call.
Sadly I haven't made progress on embedding the assembler and linker, and
I don't see this happening before feature freeze for gcc 6 (November
9th), as I'm working on a big overhaul of gcc's diagnostics (adding
underlining of source code ranges) and various other usability
improvements.
Dave
next prev parent reply other threads:[~2015-10-19 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm [this message]
2015-01-01 0:00 ` Dibyendu Majumdar
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=1445263982.3998.16.camel@surprise \
--to=dmalcolm@redhat.com \
--cc=jit@gcc.gnu.org \
--cc=mobile@majumdar.org.uk \
/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).