public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* problem with lto
@ 2024-04-23 14:53 王淳洋
  2024-04-24  8:48 ` Arsen Arsenović
  0 siblings, 1 reply; 2+ messages in thread
From: 王淳洋 @ 2024-04-23 14:53 UTC (permalink / raw)
  To: gcc-help

[-- Attachment #1: Type: text/plain, Size: 297 bytes --]

Hello, I am using -flto when building nginx, but got lower benchmark
scores, about -1%~-2%, which makes me confused.
I am wondering if there are other options to be combined with -flto, to
make the best optimization.
By the way, will lto acts on the process of merging .o to generate .a .
Thanks.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: problem with lto
  2024-04-23 14:53 problem with lto 王淳洋
@ 2024-04-24  8:48 ` Arsen Arsenović
  0 siblings, 0 replies; 2+ messages in thread
From: Arsen Arsenović @ 2024-04-24  8:48 UTC (permalink / raw)
  To: 王淳洋 via Gcc-help; +Cc: 王淳洋

[-- 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 --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-04-24  8:48 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-23 14:53 problem with lto 王淳洋
2024-04-24  8:48 ` Arsen Arsenović

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).