From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 36491 invoked by alias); 11 Jun 2015 20:47:41 -0000 Mailing-List: contact jit-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: Sender: jit-owner@gcc.gnu.org Received: (qmail 36479 invoked by uid 89); 11 Jun 2015 20:47:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.98.7 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-Spam-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org X-Spam-Level: X-HELO: mail-yh0-f43.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=dtBV2qsKAKrZKeAON7WMMJ7N13/RpY72ZDVBvJx7IWA=; b=cOhX6AiMqF4rVrhWhOnZn/CgQYhrJmRLOOTV7mNV4aJY/0jh/4PXHpXBQEV6qklHWv xHiDTZ5pQrqaeovpkZjzlnz/RoSXnv1XHCVVAcHAe13R1F1+Xxl/BrTyDLOx0Hb5W0ox dKDKhh+yGe/AGl9QTzEQ25rC2VJMpRgiMhiWklhMtVLlSbs+4FlR5RR1OoE034qZJUiq 3jWZr9iJ7k+/9dhS6EHBldduVr42pVwh+O1giGeRQTw45WBfvN55mLs+bBazV8ZwljFc 3NkbH5AWIAcJSDFHy+3xmnWIhtQe3qmBnfGJZfzv+FOr4CctgZTL354hv6GHOpZRq9UE rEpA== X-Gm-Message-State: ALoCoQkLr3M+v1I3MIyRI2sooQtr+LnhviEXstubCQcFGsSv0QM3Kz2RQ5BdyKHbOxEQXYj8h4pG MIME-Version: 1.0 X-Received: by 10.129.27.6 with SMTP id b6mr14237665ywb.134.1434055658341; Thu, 11 Jun 2015 13:47:38 -0700 (PDT) In-Reply-To: <1434054869.12727.207.camel@surprise> References: <1434054685.12727.205.camel@surprise> <1434054869.12727.207.camel@surprise> Date: Thu, 01 Jan 2015 00:00:00 -0000 Message-ID: Subject: Re: Basic blocks, jump targets and locals From: Dibyendu Majumdar To: David Malcolm Cc: jit@gcc.gnu.org Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2015-q2/txt/msg00047.txt.bz2 On 11 June 2015 at 21:34, David Malcolm 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.