All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Anand Gadiyar <gadiyar@ti.com>, Xuanhao Shi <x-shi@ti.com>,
	Suniel Mahesh <sunil@amarulasolutions.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/4] package/arm-gnu-toolchain: revert to version 10
Date: Sun, 31 Jul 2022 09:28:38 +0200	[thread overview]
Message-ID: <20220731092838.534104d3@windsurf> (raw)
In-Reply-To: <3a838cf0-9121-4069-60d4-2601b16a801c@benettiengineering.com>

Hello,

On Sun, 31 Jul 2022 02:28:49 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> have you tried any possible work-around for this ^^^ bug?
> At the moment I don't see any other build failure using
> gcc-arm-11.2-2022.02-x86_64-arm-none-eabi, probably because every
> package that is built with it doesn't have float type in the code(I
> presume).

The arm-gnu-toolchain package is not widely used. It's only a few
specific ARM Trusted Firmware configurations that use it for the
moment, therefore this package is never exercised in the autobuilders,
and only by a few defconfigs.

> Does the gcc bug show up while building ti-k3-image-gen or ti-k3-r5-loader?
> 
> I'd prefer to find a work-around if possible rather than downgrading
> host-arm-gnu-toolchain, also because this would impact another package
> that depends on it:
> arm-trusted-firmware
> 
> Please let me know, maybe I can help finding a work-around for that
> float ICE.

It's not an ICE. What happens is that this gcc toolchain has been
compiled for a too recent x86-64 CPU core (the host binary of gcc).
Therefore if you use this toolchain on a slightly too old x86-64
machine, it will break.

Reverting to 10.x is fine here: Linaro (who produces the toolchain) has
acknowledged the problem, and will generate an updated 11.x toolchain
at some point in the future.

Best regards,

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:[~2022-07-31  7:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 16:40 [Buildroot] [PATCH v2 0/4] add support for TI's AM6X boards Xuanhao Shi via buildroot
2022-07-28 16:40 ` [Buildroot] [PATCH v2 1/4] package/arm-gnu-toolchain: revert to version 10 Xuanhao Shi via buildroot
2022-07-31  0:28   ` Giulio Benetti
2022-07-31  7:28     ` Thomas Petazzoni via buildroot [this message]
2022-08-01 17:56   ` Thomas Petazzoni via buildroot
2022-07-28 16:40 ` [Buildroot] [PATCH v2 2/4] boot/ti-k3-r5-loader: add new package Xuanhao Shi via buildroot
2022-07-31  0:54   ` Giulio Benetti
2022-07-31  8:27     ` Thomas Petazzoni via buildroot
2022-07-31 10:10       ` Giulio Benetti
2022-08-02 16:23   ` Giulio Benetti
2022-07-28 16:40 ` [Buildroot] [PATCH v2 3/4] boot/ti-k3-image-gen: " Xuanhao Shi via buildroot
2022-07-31  1:04   ` Giulio Benetti
2022-07-31  8:30     ` Thomas Petazzoni via buildroot
2022-07-28 16:40 ` [Buildroot] [PATCH v2 4/4] board/ti: add new boards Xuanhao Shi via buildroot
2022-07-31  1:15   ` Giulio Benetti
2022-07-31  8:32     ` Thomas Petazzoni via buildroot
2022-08-02 16:40   ` Giulio Benetti
2022-08-02 16:48     ` Giulio Benetti

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=20220731092838.534104d3@windsurf \
    --to=buildroot@buildroot.org \
    --cc=gadiyar@ti.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=sunil@amarulasolutions.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=x-shi@ti.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.