From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: sotrdg sotrdg <euloanty@live.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: GCC's thin lto PLEASE
Date: Mon, 25 Mar 2024 08:17:35 +0000 [thread overview]
Message-ID: <CAH6eHdT2V+bYU69gy-RkHtvVvJV65sehHuOta0d_raNZ+V63Hg@mail.gmail.com> (raw)
In-Reply-To: <SA1PR11MB71308D4BA14DBFD5792BAD27B2362@SA1PR11MB7130.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 223 bytes --]
On Mon, 25 Mar 2024, 02:19 sotrdg sotrdg via Gcc-help, <gcc-help@gcc.gnu.org>
wrote:
> it is extremely hard to even get code compile nowadays due to its slowness.
>
Isn't the solution to slowness just ... waiting longer?
prev parent reply other threads:[~2024-03-25 8:17 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
2024-03-25 8:17 ` Jonathan Wakely [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=CAH6eHdT2V+bYU69gy-RkHtvVvJV65sehHuOta0d_raNZ+V63Hg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=euloanty@live.com \
--cc=gcc-help@gcc.gnu.org \
/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).