From: "Martin Liška" <mliska@suse.cz>
To: Dongjiu Geng <gengdongjiu1@gmail.com>, gcc@gcc.gnu.org
Subject: Re: what is the difference with and without crc extension support
Date: Thu, 3 Mar 2022 14:48:42 +0100 [thread overview]
Message-ID: <ca546805-24c5-4fc7-7d2e-137c496835c3@suse.cz> (raw)
In-Reply-To: <CABSBigQ5vBkj-CtQuDMfCVmYxVQ9est_2LXMZ8Heu5Y1Cixd+g@mail.gmail.com>
On 3/3/22 14:41, Dongjiu Geng via Gcc wrote:
> Hi,
> My program does not use CRC instructions，but I find the compiled
> binary has much difference between using "-march=armv8-a+crc" and
> using "-march=armv8-a". Even stranger, when I use
> "-march=armv8-a+crc", I find my compiled binary can not run. but when
> I change -O2 to -O0 based on "-march=armv8-a+crc", it can run. I do
> not know what is the reason.. can you answer it? Thanks.
Hello.
Please report bug here:
https://gcc.gnu.org/bugzilla/
and attach a pre-processed source file:
https://gcc.gnu.org/bugs/
Martin
next prev parent reply other threads:[~2022-03-03 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 13:41 Dongjiu Geng
2022-03-03 13:48 ` Martin Liška [this message]
2022-03-03 13:52 ` Dongjiu Geng
2022-03-04 13:05 ` Martin Liška
2022-03-04 18:20 ` Richard Earnshaw
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=ca546805-24c5-4fc7-7d2e-137c496835c3@suse.cz \
--to=mliska@suse.cz \
--cc=gcc@gcc.gnu.org \
--cc=gengdongjiu1@gmail.com \
/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).