From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: David Malcolm <dmalcolm@redhat.com>
Cc: jit@gcc.gnu.org
Subject: Re: Basic blocks, jump targets and locals
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <CACXZuxcuT8BspW+ZG-Kxjmekg2X17PS+OgZcRB8EQN0NRDj+sw@mail.gmail.com> (raw)
In-Reply-To: <1434054869.12727.207.camel@surprise>
On 11 June 2015 at 21:34, David Malcolm <dmalcolm@redhat.com> wrote:
> BTW, you may want to use gcc_jit_block_add_comment:
> https://gcc.gnu.org/onlinedocs/jit/topics/functions.html#gcc_jit_block_add_comment
>
> which lets you add arbitrary comments as "statements" into the libgccjit
> IR, so it shows up in the various debug dumps. I've found this to be
> hugely valuable when debugging compilation of bytecode into libgccjit.
Cool. I will try that to annotate the blocks with the bytecode
instruction - that will be very useful for debugging.
next prev parent reply other threads:[~2015-06-11 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar [this message]
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
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=CACXZuxcuT8BspW+ZG-Kxjmekg2X17PS+OgZcRB8EQN0NRDj+sw@mail.gmail.com \
--to=mobile@majumdar.org.uk \
--cc=dmalcolm@redhat.com \
--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).