From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Kory Maincent <kory.maincent@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/arm-gnu-a-toolchain: bump to version 10.3-2021.07
Date: Sun, 19 Sep 2021 15:09:04 +0200 [thread overview]
Message-ID: <20210919150904.04051568@windsurf> (raw)
In-Reply-To: <ecec6557-9d20-134b-497c-e6c7e55deee6@mind.be>
Hello,
On Sun, 19 Sep 2021 14:35:56 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> > -ARM_GNU_A_TOOLCHAIN_VERSION = 9.2-2019.12
> > -ARM_GNU_A_TOOLCHAIN_SITE = https://developer.arm.com/-/media/Files/downloads/gnu-a/$(ARM_GNU_A_TOOLCHAIN_VERSION)/binrel
> > -ARM_GNU_A_TOOLCHAIN_SOURCE = gcc-arm-$(ARM_GNU_A_TOOLCHAIN_VERSION)-x86_64-arm-none-eabi.tar.xz
> > +ARM_GNU_A_TOOLCHAIN_VERSION = 10.3-2021.07
> > +ARM_GNU_A_TOOLCHAIN_SITE = https://developer.arm.com/-/media/Files/downloads/gnu-rm/$(ARM_GNU_A_TOOLCHAIN_VERSION)
> > +ARM_GNU_A_TOOLCHAIN_SOURCE = gcc-arm-none-eabi-$(ARM_GNU_A_TOOLCHAIN_VERSION)-x86_64-linux.tar.bz2
>
> Err, this can't be right... 'gnu-rm' stands for "GNU-based toolchain for
> Cortex-R and Cortex-M", and "arm-none-eabi" means it's a toolchain without libc...
>
> So either someone made a huge mistake at ARM, or you haven't actually tested
> this patch :-)
It was tested to build code for a Cortex-M4.
This package was originally introduced to build ARM 32-bit code in the
context of TF-A (boot/arm-trusted-firmware/). At the very beginning,
was submitted by a Marvell person, who also had to build code for a
Cortex-M3 co-processor IIRC, but then was taken over by a person from
Amarula, who needed it to build ARM 32-bit code running on a Cortex-A.
If it's truly a bare-metal toolchain with no libraries, it should not
matter, right? You just pass to gcc -march=XYZ, and it will produce the
right code. However, my understanding is that those bare-metal
toolchains do have some libraries built for the target, which can
potentially get linked with the code produced.
So, long story short: do we need arm-gnu-a-toolchaind and
arm-gnu-rm-toolchain packages ?
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-09-19 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 8:16 [Buildroot] [PATCH] package/arm-gnu-a-toolchain: bump to version 10.3-2021.07 Kory Maincent
2021-09-19 12:35 ` Arnout Vandecappelle
2021-09-19 13:09 ` Thomas Petazzoni [this message]
2021-09-20 9:18 ` Arnout Vandecappelle
2021-09-20 12:01 ` Thomas Petazzoni
2021-09-20 18:52 ` Arnout Vandecappelle
2021-09-23 19:55 ` Thomas Petazzoni
2021-09-23 21:20 ` Arnout Vandecappelle
2021-11-30 10:37 ` Köry Maincent
2021-12-30 15:59 ` Thomas Petazzoni
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=20210919150904.04051568@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=kory.maincent@bootlin.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 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.