From: Aldy Hernandez <aldyh@redhat.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: gcc-patches@gcc.gnu.org, jit@gcc.gnu.org
Subject: Re: [debug-early, jit] Port of jit to debug-early
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <5571FA67.7090500@redhat.com> (raw)
In-Reply-To: <1433530834-2426-1-git-send-email-dmalcolm@redhat.com>
On 06/05/2015 03:00 PM, David Malcolm wrote:
> "jit" isn't part of "all" languages, and currently fails to build on
> the aldyh/debug-early branch:
The debug-early work is now in mainline. Feel free to commit when you
deem appropriate, since you are the jit maintainer ;-).
> static void
> -jit_langhook_write_globals (void)
> +jit_langhook_post_compilation_parsing_cleanups (void)
> {
> gcc::jit::playback::context *ctxt = gcc::jit::active_playback_ctxt;
> gcc_assert (ctxt);
> JIT_LOG_SCOPE (ctxt->get_logger ());
>
> - ctxt->write_global_decls_1 ();
> -
> - /* This is the hook that runs the middle and backends: */
> - symtab->finalize_compilation_unit ();
> -
> - ctxt->write_global_decls_2 ();
> + ctxt->finalize_global_decls ();
This hook gets called after the compilation proper has run, and we're
trying to avoid it. We're trying to get all the front-ends to finish
their thing and avoid depending on the compilation proper.
Can you not get this to work without running finalize_global_decls after
the compilation proper? If not, then I see no problem with your
patch....after all, C++ is still using this hook :(.
Thanks for working on this.
Aldy
next prev parent reply other threads:[~2015-06-05 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 David Malcolm
2015-01-01 0:00 ` Aldy Hernandez [this message]
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Aldy Hernandez
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=5571FA67.7090500@redhat.com \
--to=aldyh@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jit@gcc.gnu.org \
/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).