From: Paul Smith <psmith@gnu.org>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>,
Kai Song <kaisong1515@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Compilation of lengthy C++ Files
Date: Wed, 25 Oct 2023 10:49:00 -0400 [thread overview]
Message-ID: <357520c5c2c85ed3e040fa886f5565ff11c51854.camel@gnu.org> (raw)
In-Reply-To: <56e28c8b-903f-4e55-965e-a1c1fc92249d@foss.arm.com>
On Wed, 2023-10-25 at 12:09 +0100, Richard Earnshaw wrote:
> Those defensive measures further slow down your compiled programs.
Just to remind, Kai Song has said multiple times in these threads that
they're not asking about improving the performance of the resulting
compiled program. They don't seem to mind if the resulting program
takes days or weeks to run.
They are asking here about how to get the compiler to successfully
compile the code, not how to make the compiled code faster.
next prev parent reply other threads:[~2023-10-25 14:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 16:04 Kai Song
2023-10-18 21:59 ` Jonathan Wakely
2023-10-19 8:36 ` Andrew Haley
2023-10-19 12:47 ` David Brown
2023-10-19 12:47 ` David Brown
2023-10-19 14:16 ` Kai Song
2023-10-19 14:26 ` Jonathan Wakely
2023-10-19 15:11 ` Kai Song
2023-10-19 16:03 ` David Brown
2023-10-20 9:32 ` Kai Song
2023-10-20 10:19 ` Jonathan Wakely
[not found] ` <CACJ51z3rYUSSe7XpcL4d2xfAhMaiVZpxWAnpkqZc1cn2DRf+uA@mail.gmail.com>
2023-10-20 21:08 ` Kai Song
2023-10-20 22:03 ` Paul Smith
2023-10-21 6:52 ` Jonathan Wakely
2023-10-21 14:10 ` Kai Song
2023-10-24 14:57 ` Paul Smith
2023-10-25 11:09 ` Richard Earnshaw
2023-10-25 14:49 ` Paul Smith [this message]
2023-10-26 11:19 ` David Brown
2023-10-19 15:15 ` David Brown
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=357520c5c2c85ed3e040fa886f5565ff11c51854.camel@gnu.org \
--to=psmith@gnu.org \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=gcc-help@gcc.gnu.org \
--cc=kaisong1515@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).