public inbox for
 help / color / mirror / Atom feed
From: Jonathan Wakely <>
To: Roman Kellner <>
Cc: Stefan Ring <>, gcc-help <>
Subject: Re: Re: gcc optimization options and lto (detailed info)
Date: Wed, 18 May 2022 11:23:09 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <trinity-1d53f520-c371-471b-b6c2-0446d6ba8184-1652865880524@3c-app-gmx-bap04>

On Wed, 18 May 2022 at 10:24, Roman Kellner wrote:
> Hi Jonathan, hi Stefan, hi all
> Thanks for your support.
> Since no detailed documenation on coding do's and dont's related to optimizations is available, except reading the code itself which will take me probably ages to get into,
> is there any common good practice how to avoid effects of optimizations:

Why do you want to avoid the effects of optimizations?

If your code is correct, then it will behave the same optimized or
unoptimized, LTO or not. I don't understand what you're so concerned
about that you think you need to tweak optimization options in precise

If you think LTO might cause problems for your OS, you can just not
use it. Don't contort the code in strange ways to solve hypothetical

  parent reply	other threads:[~2022-05-18 10:23 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 [this message]
     [not found]       ` <trinity-dba8f838-b88d-491b-a582-c9be885cb09e-1652951565751@3c-app-gmx-bs42>
2022-05-19  9:33         ` Re: " 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 \ \ \ \ \ \

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