From: sotrdg sotrdg <euloanty@live.com>
To: NightStrike <nightstrike@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: RE: GCC's thin lto PLEASE
Date: Mon, 25 Mar 2024 12:14:31 +0000 [thread overview]
Message-ID: <SA1PR11MB7130B88A7D578A95AB881D00B2362@SA1PR11MB7130.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAF1jjLtmBqE5MviD63nbFZwBgh7MKwO79AzYnCbi13-pZtFopA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
Try to build it with llvm/clang. It would be ridiculously slow + oom.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
________________________________
From: NightStrike <nightstrike@gmail.com>
Sent: Monday, March 25, 2024 3:01:00 AM
To: sotrdg sotrdg <euloanty@live.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: GCC's thin lto PLEASE
On Sun, Mar 24, 2024, 22:18 sotrdg sotrdg via Gcc-help <gcc-help@gcc.gnu.org<mailto:gcc-help@gcc.gnu.org>> wrote:
gosh. GCC compiles so slow compared to clang with thin lto for C++, since the translation unit tends to be big, without thin lto, it is extremely hard to even get code compile nowadays due to its slowness.
Did you try the option "-fno-fat-lto-objects" ?
Also, to get significant speedup, use -flto=auto. That will run parallel jobs.
Read https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html for more fun. The LTO section is extensive.
next prev parent reply other threads:[~2024-03-25 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 2:17 sotrdg sotrdg
2024-03-25 7:01 ` NightStrike
2024-03-25 12:14 ` sotrdg sotrdg [this message]
2024-03-25 8:17 ` Jonathan Wakely
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=SA1PR11MB7130B88A7D578A95AB881D00B2362@SA1PR11MB7130.namprd11.prod.outlook.com \
--to=euloanty@live.com \
--cc=gcc-help@gcc.gnu.org \
--cc=nightstrike@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).