From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout-p-103.mailbox.org (mout-p-103.mailbox.org [IPv6:2001:67c:2050:0:465::103]) by sourceware.org (Postfix) with ESMTPS id 87E2B3861001 for ; Wed, 24 Apr 2024 08:48:56 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 87E2B3861001 Authentication-Results: sourceware.org; dmarc=pass (p=reject dis=none) header.from=aarsen.me Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=aarsen.me ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 87E2B3861001 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2001:67c:2050:0:465::103 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1713948540; cv=none; b=egjg5hfMj+mNywAzrjyOGDsI2ozeADfNIRaFQtyo8fvGRQtgeqS80pKp0jG4adJraDC/B4sVc+M5JI9qN8doyvftPiItqBbWffgDpVUyvE/h00Ytf/JmmXKhGrIIqphNN0UGD7C1kiwzCXYvl59r35W+Kq0iATZZs264CB6LjUA= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1713948540; c=relaxed/simple; bh=uNeI5T0QfDWuyVvTVMLiGL0xLtY9r6n08Zk4jKCU9sU=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=VE3EEox5Ogmn1na7UKIsXoGE6KNc6kD1iDc8RwpBsCXekhGWiAbcaC56cMNUe5kec5KeuyzXZ2tfFlp6dle9nfEv5IyqE4YrHhxMXaB+/SVhS6+nqYZubNacmj7BoKg4gzfp89r0jzrKs4bwDhayNmLkWOjwhtIEH/+Uy1tNXRQ= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:b231:465::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-103.mailbox.org (Postfix) with ESMTPS id 4VPXhh5MY3z9ssr; Wed, 24 Apr 2024 10:48:52 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aarsen.me; s=MBO0001; t=1713948532; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=MfX9en0GA6XzR5GxW42R2D8sKMVwJtngDQ8J7WhI7XQ=; b=YT7Qc7BxPvOCcarDZasd1ehWm+JbL6BFU76GyQTc2EO7cxIJX3pI9flt0ave/BJ5V8wWfb hLL8DiqGQWPVUZZQkMCDfFeWLb16c57odGKuQ/70YdZlJw80CPS/n+gG+LG2Zl+s0SWLXn +4XQg1HCClBMhOKH+QGhLrJvNONIAR4hAk4nE80xeaLRV2ncFYgWe0ifj/GD1sH7Lt4eww 2A10k8qgwFs0rnPSaI1Q8RYl6KRQsLTI7DWXoltq1lgX3MMJDvSALw2aEYKIxs7L4zQUTG 5nwMuo0NFcsUTGl5sZpwJA38WoCSub/ec7GwdBI0qjW0vKZ5aJUv3VVXQ65z5A== From: =?utf-8?Q?Arsen_Arsenovi=C4=87?= To: =?utf-8?B?546L5rez5rSL?= via Gcc-help Cc: =?utf-8?B?546L5rez5rSL?= Subject: Re: problem with lto In-Reply-To: (=?utf-8?B?IueOi+a3s+a0iw==?= via Gcc-help"'s message of "Tue, 23 Apr 2024 22:53:44 +0800") References: Date: Wed, 24 Apr 2024 10:48:50 +0200 Message-ID: <87le53b0y5.fsf@aarsen.me> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Rspamd-Queue-Id: 4VPXhh5MY3z9ssr X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00,BODY_8BITS,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_INFOUSMEBIZ,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, =E7=8E=8B=E6=B7=B3=E6=B4=8B via Gcc-help writes: > Hello, I am using -flto when building nginx, but got lower benchmark > scores, about -1%~-2%, which makes me confused. That's not impossible, as benchmark results can be influenced by a myriad of factors. > I am wondering if there are other options to be combined with -flto, to > make the best optimization. The usual optimization flags. And, as usual, there's no silver bullet. > By the way, will lto acts on the process of merging .o to generate .a > . No - only at time of use of the '.a'. =2D-=20 Arsen Arsenovi=C4=87 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iIYEARYKAC4WIQT+4rPRE/wAoxYtYGFSwpQwHqLEkwUCZijHchAcYXJzZW5AYWFy c2VuLm1lAAoJEFLClDAeosSTCckA/REPaaCcY7qJzrD0oM0Llb0KzkttlxZHNsoB osCLNzefAQD5R9FEAFsvG5WgNHa+MDGIrm7e5LbBx0QIkiMumkNdBg== =Q4KW -----END PGP SIGNATURE----- --=-=-=--