From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 122828 invoked by alias); 16 Apr 2019 09:56:16 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 122611 invoked by uid 89); 16 Apr 2019 09:56:16 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=our X-HELO: mail-lj1-f171.google.com Received: from mail-lj1-f171.google.com (HELO mail-lj1-f171.google.com) (209.85.208.171) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 16 Apr 2019 09:56:14 +0000 Received: by mail-lj1-f171.google.com with SMTP id p14so18511201ljg.5 for ; Tue, 16 Apr 2019 02:56:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=WybRuOVrzZdcL/xO/mWCOxp/dK6Scf9ncneWVra8oTE=; b=bkG8NdiEgs+4todeQgZiDqk6QCt5he05BDPhstvzra7ujVcqnRGi5N/0CDdF8Pw4xa ZS8P6wHoPYG5AMwQ6xztF0Xh70zBCYJOmbLm5UVsHif8+XI3HRkCUv/1tFUyJIG9Hxh1 WQKtfEFv1AP/EgNqrH/KNgMwNXFAxiHXsrRpqkCAQu2gzL7Lh1Ot/4rLqMFOohKnOf+6 pEm50DnNLBzAJSv9YDdQx5yRzalUOZJpHaDw6WzeEqUaXZi+XfP2rSg92DVY216VczZo OQPDcNNP5wB+bgtXt/fVMd6RwqGSspZhhJhaD8swmIdIMGKeE7NH9kkaMy/hqP4JZlNJ BZMw== MIME-Version: 1.0 References: <6f547f38-1751-c003-b5ae-52dae776d39a@suse.cz> <65289853-0db4-4645-74b4-869443addf1a@suse.cz> <20190415133326.GT21066@tucnak> In-Reply-To: From: Richard Biener Date: Tue, 16 Apr 2019 09:56:00 -0000 Message-ID: Subject: Re: GCC 8 vs. GCC 9 speed and size comparison To: Michael Matz Cc: =?UTF-8?Q?Martin_Li=C5=A1ka?= , Jakub Jelinek , GCC Development , Jan Hubicka , Martin Jambor Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2019-04/txt/msg00161.txt.bz2 On Tue, Apr 16, 2019 at 10:53 AM Michael Matz wrote: > > Hello Martin, > > On Tue, 16 Apr 2019, Martin Li=C5=A1ka wrote: > > > Yes, except kdecore.cc I used in all cases .ii pre-processed files. I'm > > going to start using kdecore.ii as well. > > If the kdecore.cc is the one from me it's also preprocessed and doesn't > contain any #include directives, I just edited it somewhat to be > compilable for different architecture. Btw, the tramp3d sources on our testers _do_ contain #include directives. Richard. > > Ciao, > Michael. > > > > > As Honza pointed out in the email that hasn't reached this mailing list > > due to file size, there's a significant change in inline-unit-growth. T= he param > > has changed from 20 to 40 for GCC 9. Using --param inline-unit-growth= =3D20 for all > > benchmarks, I see green numbres for GCC 9! > > > > Martin > > > > > > > > > > > Ciao, > > > Michael. > > > > > > >