From: "Arsen Arsenović" <arsen@aarsen.me>
To: "王淳洋 via Gcc-help" <gcc-help@gcc.gnu.org>
Cc: 王淳洋 <koule2333@gmail.com>
Subject: Re: problem with lto
Date: Wed, 24 Apr 2024 10:48:50 +0200 [thread overview]
Message-ID: <87le53b0y5.fsf@aarsen.me> (raw)
In-Reply-To: <CAPRNTujinOV4k7FyoJi7H-VpFjAdeXLURfsMgL78=GcaycBysA@mail.gmail.com> (=?utf-8?B?IueOi+a3s+a0iw==?= via Gcc-help"'s message of "Tue, 23 Apr 2024 22:53:44 +0800")
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
Hi,
王淳洋 via Gcc-help <gcc-help@gcc.gnu.org> 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'.
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
prev parent reply other threads:[~2024-04-24 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 14:53 王淳洋
2024-04-24 8:48 ` Arsen Arsenović [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87le53b0y5.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=gcc-help@gcc.gnu.org \
--cc=koule2333@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).