From: NightStrike <nightstrike@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: A priori profile optimization
Date: Wed, 14 Apr 2021 07:01:48 -1000 [thread overview]
Message-ID: <CAF1jjLt8jKFMqCVBu66LV6PQtaNXqecH=tWiwv-fyY7PdjYsNA@mail.gmail.com> (raw)
In-Reply-To: <CAF1jjLv2JpKvyRxPX_X1++qY2mXxfzyz-Nqmy4-vgnjWBWrUqg@mail.gmail.com>
On Sun, Dec 6, 2020, 18:36 NightStrike <nightstrike@gmail.com> wrote:
> Is there a way to get gcc to tell you if it could optimize better with
> profiling information? In other words, it'd be nice to know how much,
> roughly speaking, profile based optimization would have an effect before
> going through the trouble of setting it up. Like, if gcc could say, "just
> fyi, i could make this loop potentially twice as fast if you give me a
> profile to work with". Or, "yeah, even with a profile, that function won't
> get much better."
>
> If it could tell me next week's lottery numbers, too, that'd be great.
> Maybe that's easier :)
>
Just wondering if this is possible.
>
prev parent reply other threads:[~2021-04-14 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 4:36 NightStrike
2021-04-14 17:01 ` NightStrike [this message]
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='CAF1jjLt8jKFMqCVBu66LV6PQtaNXqecH=tWiwv-fyY7PdjYsNA@mail.gmail.com' \
--to=nightstrike@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).