All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] arch: add support for loongarch64
Date: Tue, 14 May 2024 10:02:17 +0200	[thread overview]
Message-ID: <20240514100217.35add5c1@windsurf> (raw)
In-Reply-To: <ZkMEATm9Efp16zRg@waldemar-brodkorb.de>

On Tue, 14 May 2024 08:26:09 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:

> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
>  arch/Config.in             | 12 ++++++++++++
>  arch/Config.in.loongarch64 | 14 ++++++++++++++
>  package/glibc/Config.in    |  1 +
>  package/musl/Config.in     |  1 +
>  4 files changed, 28 insertions(+)
>  create mode 100644 arch/Config.in.loongarch64

This needs an entry in the DEVELOPERS file.

Is this architecture supported in all versions of binutils/gcc/gdb we
support?

> diff --git a/arch/Config.in.loongarch64 b/arch/Config.in.loongarch64
> new file mode 100644
> index 0000000000..2b5bac095d
> --- /dev/null
> +++ b/arch/Config.in.loongarch64
> @@ -0,0 +1,14 @@
> +config BR2_ARCH
> +	default "loongarch64"
> +
> +config BR2_NORMALIZED_ARCH
> +	default "loongarch"
> +
> +config BR2_ENDIAN
> +	default "LITTLE"
> +
> +config BR2_READELF_ARCH_NAME
> +	default "LoongArch"
> +

Based on the gcc documentation, I see two -march values:

     ‘loongarch64’
          A generic CPU with 64-bit extensions.
     ‘la464’
          LoongArch LA464 CPU with LBT, LSX, LASX, LVZ.

And also 3 ABIs:

     ‘lp64d’
          Uses 64-bit general purpose registers and 32/64-bit
          floating-point registers for parameter passing.  Data model is
          LP64, where ‘int’ is 32 bits, while ‘long int’ and pointers
          are 64 bits.
     ‘lp64f’
          Uses 64-bit general purpose registers and 32-bit
          floating-point registers for parameter passing.  Data model is
          LP64, where ‘int’ is 32 bits, while ‘long int’ and pointers
          are 64 bits.
     ‘lp64s’
          Uses 64-bit general purpose registers and no floating-point
          registers for parameter passing.  Data model is LP64, where
          ‘int’ is 32 bits, while ‘long int’ and pointers are 64 bits.

Should we do something about this?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-05-14  8:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14  6:26 [Buildroot] [PATCH 1/3] arch: add support for loongarch64 Waldemar Brodkorb
2024-05-14  8:02 ` Thomas Petazzoni via buildroot [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=20240514100217.35add5c1@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wbx@openadk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.