From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jit-return-698-listarch-jit=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 124487 invoked by alias); 30 Jun 2015 21:15:45 -0000
Mailing-List: contact jit-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:jit@gcc.gnu.org>
List-Help: <mailto:jit-help@gcc.gnu.org>
List-Subscribe: <mailto:jit-subscribe@gcc.gnu.org>
Sender: jit-owner@gcc.gnu.org
Received: (qmail 124438 invoked by uid 89); 30 Jun 2015 21:15:44 -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-f173.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:content-type;
        bh=UlXnkQM34ORYb9Oi6joLEAmzC0sIxYypRAXxGua18WY=;
        b=ZXB0wYn5VlPvA3MMxjM3nPiqFNxOcbqFmkHrKxeFNmjrwuDYOT1Polah8w0Eus3m11
         BphC/TyX5ZUHyxp/5c7kBZ5ict2YHOoT+Le4E1qmzOXNdfSp0KJlyJ+jiL+cN6gQVwU+
         jQ4r5fCpfyLTL3GHJ6WwEE9KtY8IWE//ykWaVb1BlhvN8R9xNhDtvUghI3xbIL9BiF8b
         4vp9zHbEyKKVzPUUCf1BTvApmQ3O3XvYOQgDcPgX21Vh11ssHzynkmgYqQb1bkJnYcvM
         IwHF4391TL37LIebjo2L+fOYpCSQlrOtx1cTmUyGQNXtb+D3SxF+gAeBGWUMtYiwv9Bu
         lDHg==
X-Gm-Message-State: ALoCoQlvEkk4DqFUBMaUCWj3iAdWkhAWPE0bPXRKact+gai3b/979+XF3sjQ3YalBZwRcdpQqmwL
MIME-Version: 1.0
X-Received: by 10.170.82.131 with SMTP id y125mr27881236yky.115.1435698938795;
 Tue, 30 Jun 2015 14:15:38 -0700 (PDT)
In-Reply-To: <CACXZuxdEF=hzoyVB=koV-MKyhTofoV3LN4w6wHMOWAP7zmb2dA@mail.gmail.com>
References: <CACXZuxdEF=hzoyVB=koV-MKyhTofoV3LN4w6wHMOWAP7zmb2dA@mail.gmail.com>
Date: Thu, 01 Jan 2015 00:00:00 -0000
Message-ID: <CACXZuxeMszkD4pCat1dR0RK=rOgQXxXX79KtXi1DtVojy3UjSw@mail.gmail.com>
Subject: Re: Stuff to include in libgccjit 5.2
From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: jit@gcc.gnu.org
Content-Type: text/plain; charset=UTF-8
X-SW-Source: 2015-q2/txt/msg00156.txt.bz2

On 30 June 2015 at 20:53, Dibyendu Majumdar <mobile@majumdar.org.uk> wrote:
> 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.
>

Pleased to report that the test suite is now working for the bytecodes
implemented so far. The bugs were all related to missing evaluations
of function call expressions. This is the most frequent mistake I am
making when porting LLVM code - in LLVM of course everything is
immediate - whereas in libgccjit one has to remember that an rvalue is
not evaluated unless it is used in a call or another expression.

I will try to implement as many op codes as I can over the weekend and
report back in case of issues.

Thanks and Regards

Dibyendu