From: Kit Chow <kitmchow@roadrunner.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: disable generation of .cold functions
Date: Thu, 5 Nov 2020 10:41:14 -0800 [thread overview]
Message-ID: <009cafac-874e-a4f6-2eba-aa845f9bb807@roadrunner.com> (raw)
In-Reply-To: <87h7q3wvqz.fsf@oldenburg2.str.redhat.com>
Hi Florian,
That did the trick. Thanks so much!
Kit
On 11/5/2020 9:37 AM, Florian Weimer wrote:
> * Kit Chow:
>
>> Is there a gcc option to disable the generation of .cold functions?
>> I can't find anything explicit in the driver source/Makefile to create
>> .cold functions.
> You could try -fno-reorder-blocks-and-partition. I just found the
> option in the documentation, so I don't know if it really works for this
> specific case, sorry.
>
> Florian
prev parent reply other threads:[~2020-11-05 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 17:15 Kit Chow
2020-11-05 17:37 ` Florian Weimer
2020-11-05 18:41 ` Kit Chow [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=009cafac-874e-a4f6-2eba-aa845f9bb807@roadrunner.com \
--to=kitmchow@roadrunner.com \
--cc=fweimer@redhat.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).