public inbox for
 help / color / mirror / Atom feed
From: Jonathan Wakely <>
To: "" <>
Cc: gcc-help <>
Subject: Re: gcc optimization options and lto (detailed info)
Date: Tue, 17 May 2022 09:30:56 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, 17 May 2022 at 07:57, muzungu--- via Gcc-help
<> wrote:
> * does every -f<xyz> have a -fno-<xyz>?

Nearly all, yes:

"Many options have long names starting with -f or with -W --- for
example, -fmove-loop-invariants, -Wformat and so on.  Most of these
have both positive and negative forms; the negative form of -ffoo is
-fno-foo.  This manual documents only one of these two forms,
whichever one is not the default."

> * would I be able able to disable single optimizations activated via -O<x> using -fno-<xyz> after -O<x>?


> * When LTO is enabled, are the optimizations only effective at link time and not during the compilation into IR (GIMPLE)?


> * Or are the optimizations effective in different stages of the build process? Are there information which options is applied when?

If a particular optimization is only effective before/during LTO I
think that will be mentioned in the manual. If it isn't mentioned,
assume it is effective at both times.

> Are there information available what the different optimizations do (which I know, is a long list) and how such unwanted optimization can be avoided respective the unwanted effects of the optimizations

No, it would be an entire book, and rapidly be outdated. All the
available documentation is already in the GCC manual. Of course the
source code is the ultimate guide, but it's not clear to follow unless
you already know how GCC works.

> * Since there is a rather long list of optimization options which would very likely exceed the command line length, what is the solution to activate a custom set of optimzations? I could not find a --configfile option or similar to replace the command line.

See the @file option.

But if you need so many options that you exceed the command-line
limits, maybe you're doing something wrong. That would be unusual.

  reply	other threads:[~2022-05-17  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17  6:56 muzungu
2022-05-17  8:30 ` Jonathan Wakely [this message]
     [not found]   ` <trinity-1d53f520-c371-471b-b6c2-0446d6ba8184-1652865880524@3c-app-gmx-bap04>
2022-05-18 10:23     ` Jonathan Wakely
     [not found]       ` <trinity-dba8f838-b88d-491b-a582-c9be885cb09e-1652951565751@3c-app-gmx-bs42>
2022-05-19  9:33         ` Jonathan Wakely
2022-05-17  8:54 ` Stefan Ring
2022-05-17 23:05 ` Segher Boessenkool

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

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