From: Segher Boessenkool <segher@kernel.crashing.org>
To: NightStrike <nightstrike@gmail.com>
Cc: David Brown <david@westcontrol.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: GCC Optimization Levels - Seeking Insights
Date: Tue, 26 Dec 2023 12:46:01 -0600 [thread overview]
Message-ID: <20231226184601.GU19790@gate.crashing.org> (raw)
In-Reply-To: <CAF1jjLtuP4_naOTWCGDq=DEUXf9XGfdZB2nBa2rZ0=gbwHqxbA@mail.gmail.com>
On Mon, Dec 25, 2023 at 11:21:45AM -0500, NightStrike via Gcc-help wrote:
> On Fri, Dec 22, 2023, 04:25 David Brown via Gcc-help <gcc-help@gcc.gnu.org>
> wrote:
> > OPTS = 0 1 2 3 g fast
>
> It's worth testing with march=native and flto, both provide easy wins if
> you can accept any implied limitations.
Also -Os is interesting.
Segher
next prev parent reply other threads:[~2023-12-26 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 19:32 Aran Nokan
2023-12-21 19:57 ` Jonathan Wakely
2023-12-22 9:24 ` David Brown
2023-12-22 10:44 ` Aran Nokan
2023-12-22 11:25 ` David Brown
2023-12-22 11:51 ` Jonathan Wakely
2023-12-22 11:52 ` Jonathan Wakely
2023-12-25 16:21 ` NightStrike
2023-12-26 18:46 ` Segher Boessenkool [this message]
2023-12-24 13:54 ` Peter0x44
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=20231226184601.GU19790@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=david@westcontrol.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).