From: Stefan Ring <stefanrin@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: gcc optimization options and lto (detailed info)
Date: Tue, 17 May 2022 10:54:03 +0200 [thread overview]
Message-ID: <CAAxjCEy9Tj-OCfh0Du0FMLL5nfqcj26+sXfQRW6qw58FeLd5UQ@mail.gmail.com> (raw)
In-Reply-To: <062812e4-e912-4eaf-876c-91006a6c47a6@gmx.net>
On Tue, May 17, 2022 at 8:56 AM muzungu--- via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> * does every -f<xyz> have a -fno-<xyz>?
I think that’s the idea.
> * would I be able able to disable single optimizations activated via -O<x> using -fno-<xyz> after -O<x>?
Yes.
> * When LTO is enabled, are the optimizations only effective at link time and not during the compilation into IR (GIMPLE)?
I would expect them to be recorded in the intermediate object file and
becoming effective during code generation, but I am not sure about
that.
> * 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.
What do you think is your maximum command line length? This should not
be a problem on any sane OS.
next prev parent reply other threads:[~2022-05-17 8:54 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
[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 [this message]
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:
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=CAAxjCEy9Tj-OCfh0Du0FMLL5nfqcj26+sXfQRW6qw58FeLd5UQ@mail.gmail.com \
--to=stefanrin@gmail.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).