From: Christer Solskogen <christer.solskogen@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: mfix-cortex-a53
Date: Fri, 8 Mar 2024 07:41:51 +0100 [thread overview]
Message-ID: <usebvg$13i$1@ciao.gmane.io> (raw)
In-Reply-To: <PAWPR08MB8982FE9A3E19B57743EA60B783202@PAWPR08MB8982.eurprd08.prod.outlook.com>
On 3/7/2024 8:09 PM, Wilco Dijkstra via Gcc-help wrote:
> Hi,
>
>> Are there any good reason for NOT having them enabled?
>
> Yes, there is a codesize and performance impact (and it can be
> nasty if you have a hot loop that crosses a page).
>
> So only use the option if you're using Cortex-A53 and you're
> unlucky enough to have an early revision with the bug.
> It is absolutely not needed for any newer core.
>
Thanks a lot!
--
chs
next prev parent reply other threads:[~2024-03-08 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 19:09 mfix-cortex-a53 Wilco Dijkstra
2024-03-08 6:41 ` Christer Solskogen [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-04 13:09 mfix-cortex-a53 Christer Solskogen
2024-03-07 15:01 ` mfix-cortex-a53 Kyrylo Tkachov
2024-03-07 16:50 ` mfix-cortex-a53 Christer Solskogen
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='usebvg$13i$1@ciao.gmane.io' \
--to=christer.solskogen@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).