public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Zvi Vered <veredz72@gmail.com>
To: Chris Packham <judge.packham@gmail.com>
Cc: crossgcc maillist <crossgcc@sourceware.org>
Subject: Re: 1.25.0: aarch64-unknown-linux-gnu with neon support
Date: Tue, 14 Jun 2022 06:20:53 +0300	[thread overview]
Message-ID: <CABRndgx9T_ntXXxVrudycDJi=7j9vpWgDXsTKGfYXBm=+vXAAw@mail.gmail.com> (raw)
In-Reply-To: <CAFOYHZBLtxg1=tAW=aT-f3fNpaHpXQpFUTQCWL7gionb1pT41Q@mail.gmail.com>

Hi Chris,

Thank you very much for your reply.
According to:
https://developer.arm.com/Processors/Cortex-A53

The architecture of Cortex-A53 is ARMv8.
Is has "Neon advanced SIMD"

I wonder how to configure crosstool 1.25.0 to fit exactly this CPU for
linux, 64bits.

Best regards,
Zvika


On Mon, Jun 13, 2022 at 12:24 PM Chris Packham <judge.packham@gmail.com>
wrote:

> On Mon, Jun 13, 2022 at 2:29 PM Zvi Vered via crossgcc
> <crossgcc@sourceware.org> wrote:
> >
> > Hello,
> >
> > I ran:
> > ct-ng aarch64-unknown-linux-gnu
> > but with this configuration, under "Target options" I can't set FPU.
> >
> >  How can I create gcc for armv8 (coretex A53), 64bit  with the option:
> > -mfpu=neon
>
> The aarch64 configs don't use the FPU option (I think because the FPU
> is required by the ARMv8 spec). Instead you probably want to use the
> -mcpu/-mtune options as per
>
> https://gcc.gnu.org/onlinedocs/gcc-12.1.0/gcc/AArch64-Options.html#AArch64-Options
>
> >
> > Thank you,
> > Zvika
> > --
> > For unsubscribe information see http://sourceware.org/lists.html#faq
>

  reply	other threads:[~2022-06-14  3:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13  9:28 Zvi Vered
2022-06-13  9:24 ` Chris Packham
2022-06-14  3:20   ` Zvi Vered [this message]
2022-06-14  4:37     ` Chris Packham

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='CABRndgx9T_ntXXxVrudycDJi=7j9vpWgDXsTKGfYXBm=+vXAAw@mail.gmail.com' \
    --to=veredz72@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=judge.packham@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).