From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] toolchain: introduce BR2_TOOLCHAIN_HAS_GCC_BUG_111001
Date: Sat, 12 Aug 2023 14:36:21 +0200 [thread overview]
Message-ID: <20230812143621.6c67dcb3@windsurf> (raw)
In-Reply-To: <ZNdwsocEpsgQ7U9J@waldemar-brodkorb.de>
On Sat, 12 Aug 2023 13:44:51 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> e2fsprogs package fails to build for the SH4 architecture due to a gcc
> 13.2.0 bug that leads to:
> during RTL pass: sh_treg_combine2
> rw_bitmaps.c: In function read_bitmaps_range_start:
> internal compiler error: Aborted
>
> Let's add gcc bug to avoid to deal with architectures in packages
> when a gcc bug arises. Let's instead deal directly with gcc
> bug number.
>
> It's been reported upstream:
> https://gcc.gnu.org/bugzilla//show_bug.cgi?id=111001
>
> No need to backport as gcc 13.20 was introduced recently in
> buildroot.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> toolchain/Config.in | 11 +++++++++++
> 1 file changed, 11 insertions(+)
Both applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-12 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 11:44 [Buildroot] [PATCH 1/2] toolchain: introduce BR2_TOOLCHAIN_HAS_GCC_BUG_111001 Waldemar Brodkorb
2023-08-12 12:36 ` 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=20230812143621.6c67dcb3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox