From: Christer Solskogen <christer.solskogen@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: mfix-cortex-a53
Date: Thu, 7 Mar 2024 17:50:22 +0100 [thread overview]
Message-ID: <uscr8e$hl8$1@ciao.gmane.io> (raw)
In-Reply-To: <PAXPR08MB692690372927887842633FA693202@PAXPR08MB6926.eurprd08.prod.outlook.com>
On 3/7/2024 4:01 PM, Kyrylo Tkachov via Gcc-help wrote:
> Hello,
>
>> -----Original Message-----
>> From: Gcc-help <gcc-help-bounces+kyrylo.tkachov=arm.com@gcc.gnu.org> On
>> Behalf Of Christer Solskogen via Gcc-help
>> Sent: Monday, March 4, 2024 1:09 PM
>> To: gcc-help@gcc.gnu.org
>> Subject: mfix-cortex-a53
>>
>> The mfix-cortex-a53 options(-mfix-cortex-a53-835769 /
>> -mno-fix-cortex-a53-835769 and -mfix-cortex-a53-843419/
>> -mno-fix-cortex-a53-843419), which of them are used by default? I mean,
>> when none of them are used.
>
> By default the fixes will not be applied i.e. the behaviour will be equivalent to -mno-fix-cortex-a53-835769 and -mno-fix-cortex-a53-843419.
> However, you (or your compiler vendor) can configure GCC during GCC compile time with the --enable-fix-cortex-a53-843419 or --enable-fix-cortex-a53-835769 options.
> In that case the fixes will be applied automatically i.e. behave as if -mfix-cortex-a53-843419 or -mfix-cortex-a53-835769 were specified.
> You can find out if your GCC distribution enables these configuration options automatically by running gcc with the "-v" option, and seeing if any of those two --enable-fix* options appear in the configuration options.
>
Thank you!
Are there any good reason for NOT having them enabled?
--
chs
next prev parent reply other threads:[~2024-03-07 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Christer Solskogen [this message]
2024-03-07 19:09 mfix-cortex-a53 Wilco Dijkstra
2024-03-08 6:41 ` 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='uscr8e$hl8$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).