From: James Greenhalgh <james.greenhalgh@arm.com>
To: Vyacheslav Barinov <v.barinov@samsung.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: AArch32 gcc mode
Date: Wed, 29 Oct 2014 09:15:00 -0000 [thread overview]
Message-ID: <20141029091519.GA20762@arm.com> (raw)
In-Reply-To: <87bnova0kl.fsf@samsung.com>
On Wed, Oct 29, 2014 at 05:48:10AM +0000, Vyacheslav Barinov wrote:
> James Greenhalgh <james.greenhalgh@arm.com> writes:
> > On Tue, Oct 28, 2014 at 05:29:15AM +0000, Slava Barinov wrote:
> >> I work now with ARM64 CPUs and wanted to check AArch32 mode, I can see
> >> several mentions in GCC source code but can't find flag which switches on
> >> AArch32 code generation.
> >>
> >> Is it possible to make current GCC generate it?
> >
> > AArch32 is the 32-bit execution state in the ARMv8 architecture. It is
> > closely related to the ARMv7 architecture, which in GCC is implemented as
> > the "arm" target. Code generation for the AArch64 execution state of the
> > ARMv8 architecture is implemented as the "aarch64" target.
> >
> > GCC has a model whereby the compiler can be built for only one target at
> > any time, so there is no flag which will generate AArch32 code from an
> > AArch64 compiler. You will need a compiler built to target "arm".
> >
> > For your use case that will mean installing two cross-compilers, one for
> > (for example) arm-none-linux-gnueabi, and one for aarch64-none-linux-gnu.
>
> That was the first thing I tried and it works partially.
> But my initial idea was to use armv8 hardware extensions like accelerated
> crypto engine.
>
> Will setting CPU model to armv8 in arm-none-linux-gnueabi toolchain make it
> possible to use all its features in 32bit code?
Initial support in the ARM port for ARMv8-A was added in GCC 4.8. Support
for the ARMv8-A Crypto extension, and for the CRC instructions, was added to
the ARM port in GCC 4.9 [1].
To enable support for the CRC intrinsics you should use:
-march=armv8-a+crc
To enable support for the Crypto intrinsics you should use:
-mfpu=crypto-neon-fp-armv8
You can look at: https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html for
more details on the available options for the ARM target.
Thanks,
James
---
[1]: GCC 4.9 Release Series Changes, New Features, and Fixes
https://gcc.gnu.org/gcc-4.9/changes.html
prev parent reply other threads:[~2014-10-29 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 5:29 Slava Barinov
2014-10-28 8:34 ` Andrew Haley
2014-10-28 9:02 ` James Greenhalgh
2014-10-28 15:16 ` Andrew Haley
2014-10-29 5:48 ` Vyacheslav Barinov
2014-10-29 9:15 ` James Greenhalgh [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=20141029091519.GA20762@arm.com \
--to=james.greenhalgh@arm.com \
--cc=gcc-help@gcc.gnu.org \
--cc=v.barinov@samsung.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).