From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30747 invoked by alias); 30 Jun 2015 19:53:20 -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 30734 invoked by uid 89); 30 Jun 2015 19:53:20 -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.5 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.5 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-yk0-f169.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:date:message-id:subject:from:to :content-type; bh=sK1/kN950PVu6OUhTvsqxPNCoUY2Io/IHpAdhxOERQ0=; b=Jq9OxWWLICp46A/GKDnV42v58jErbyasp8qgZ1eKPsfI0YjkwjfKCTzyie9BsmlibY aKpKKof7WtfZYk7ON/JLFra/x3AqncUs/F4EaNBFFlOEQ9RdDRnINMXwKOxQErTE26py Ew+LN9zoNiJ/qBPNHLxEUBHZXYaKhwfEaCHnh1/m+TGRPe/0nhsTbqJ6SkIajve1EBef 7ln6Eijs66W4YvVBzMue7HqifVY5gFqWWceKnEb/q6WyHaMzhhtNLdo8+YfUWREXTk8/ 6lq6r6+zAeg1kyBH+WGkvR6neYnHo7l8cwkDgAoEF8DNFcHIHiQh0Dx6oz94OMnEONC6 HbkQ== X-Gm-Message-State: ALoCoQk+K0T0pj52+avnCW6akCqAdYNco9KxvBRd0IF0Z+0XeONJ5UsidU1ZL1ugkByC5Wl3KWJG MIME-Version: 1.0 X-Received: by 10.13.212.199 with SMTP id w190mr11877145ywd.57.1435693997263; Tue, 30 Jun 2015 12:53:17 -0700 (PDT) Date: Thu, 01 Jan 2015 00:00:00 -0000 Message-ID: Subject: Stuff to include in libgccjit 5.2 From: Dibyendu Majumdar To: jit@gcc.gnu.org Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2015-q2/txt/msg00153.txt.bz2 Hi Dave, Realise the deadline for 5.2 is close, but just wanted to let you know that as I compile bytecodes I tend to run standard Lua test suite. I am finding that the test suite fails at present. This could be due to bugs in my code or bugs in libgccjit - it takes me some time to isolate each issue into a small test case and then debug. In an ideal world I would like to complete the implementation of all the major bytecodes (at least to a level currently implemented in LLVM), and be able to successfully run all tests. It would then be nice if I discover any libgccjit bugs then the fixes for these to be included in 5.2. But not sure whether all this is possible before the 5.2 deadline. Thanks and Regards Dibyendu