From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20802 invoked by alias); 27 Jul 2015 22:52:26 -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 20789 invoked by uid 89); 27 Jul 2015 22:52:26 -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-ig0-f180.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=Zxf7nM7UwolOUT3de39w7NIrznRsSx1m0ti3PYHAdm0=; b=JHKs8VWg92eM4EsF4XMLlHYsNMiK4QXYbIae8eJsZCC3mBNQqU4lQ1in4sMOOiD242 W65e/vY79UFc+QwZs5tFnRoS9VwepsfzHMfa1ZZoUlrEBHLsn45V/8Qq8GonGTd1t4rP Xfpjy1Ir8XCEIieiJ/257vLzJGI7nY2K9ILQpGlHEBV0W4Rn0IS8h7M6a/gdQVq+m5PC oXLB063QuvTlZx4U7DEq5UFphCUMVj57aKSiFqeS1Y30FMcvJAjcr1tvBRC6+XOMt+CK 0T8kIzEcqi5GvWxRfgIV/JSCujEkizygea28JNffeSDSTSCfrYWfbXEOXzHTD6HtsvmH zeOg== X-Gm-Message-State: ALoCoQnZWrVmawavDSNt7kJP3ccacE5b2RP17ZPGsErxXu84ajQTyAcO4tcPGbEm5vx8SOCvOxSB MIME-Version: 1.0 X-Received: by 10.50.142.69 with SMTP id ru5mr413809igb.61.1438037542956; Mon, 27 Jul 2015 15:52:22 -0700 (PDT) In-Reply-To: <55B6AEAE.9030806@starynkevitch.net> References: <1438028999.15571.92.camel@surprise> <55B6AEAE.9030806@starynkevitch.net> Date: Thu, 01 Jan 2015 00:00:00 -0000 Message-ID: Subject: Re: JIT compilation speed From: Dibyendu Majumdar To: Basile Starynkevitch Cc: jit@gcc.gnu.org Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2015-q3/txt/msg00116.txt.bz2 On 27 July 2015 at 23:20, Basile Starynkevitch wrote: >>> Is there a timeframe for the performance improvements to the JIT >>> compilation speed? >> >> The patch kit I posted here: >> https://gcc.gnu.org/ml/gcc-patches/2015-06/msg00116.html >> gives about a 5x speedup (from about 50ms down to about 10ms on my box), > Ok, that seems good improvement. I don't have a specific benchmark but I have noticed that when I enable full compilation the Lua test suite takes 4-5 times longer to run compared to LLVM - in both cases the JIT compilation time dominates - so improvement of 5x may put libgccjit in the same ballpark as LLVM. That would be good enough to start with. > > So, for Dibyendu Majumdar: if the GCCJIT compilation time matters a lot to > you in RAVI and the performance of the emitted machine code matters much > less to you, I am afraid that GCCJIT is not the optimal library for your > needs in RAVI (using GNU lightning or asmjit would make JIT-ing time much > faster, at the expense of a produced machine code which runs 2 to 5 times > slower than what GCCJIT can achieve with -O1). > Yes understand that - I think that libgccjit needs to be at least as efficient as LLVM - that should be good enough. Regards Dibyendu