From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Romain Naour <romain.naour@gmail.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] toolchain: introduce BR2_TOOLCHAIN_HAS_GCC_BUG_83143
Date: Mon, 30 Aug 2021 23:59:51 +0200 [thread overview]
Message-ID: <20210830235951.24b82f6d@windsurf> (raw)
In-Reply-To: <20869f88-4ac4-a4e2-268b-c8d364298583@benettiengineering.com>
Hello Giulio,
On Sun, 29 Aug 2021 23:49:57 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> I try with another sh arch then I try to build ruby and check if the
> error is the same, that is very likely to happen and then I could
> transform BR2_sh4 to BR2_sh. And same goes for other sh4 bugs already
> present. But need to re-test them.
To be honest, I wouldn't bother testing all possible SuperH
architecture variants. If one issue affects SH4, just assume it affects
all SuperH variants, and be done with it. SuperH is basically dead, and
the only products using SuperH are under maintenance mode so I don't
think we should put too much effort in determining specifically which
variant of SuperH is affected by each specific gcc bug.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-30 22:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 22:34 [Buildroot] [PATCH 0/2] Add and workaround gcc bug 83143 Giulio Benetti
2021-08-27 22:34 ` [Buildroot] [PATCH 1/2] toolchain: introduce BR2_TOOLCHAIN_HAS_GCC_BUG_83143 Giulio Benetti
2021-08-28 12:06 ` Arnout Vandecappelle
2021-08-28 12:39 ` Giulio Benetti
2021-08-29 15:23 ` Arnout Vandecappelle
2021-08-29 21:49 ` Giulio Benetti
2021-08-30 21:59 ` Thomas Petazzoni [this message]
2021-08-31 17:37 ` [Buildroot] [PATCH v2 0/2] Add and workaround gcc bug 83143 Giulio Benetti
2021-08-31 17:37 ` [Buildroot] [PATCH v2 1/2] toolchain: introduce BR2_TOOLCHAIN_HAS_GCC_BUG_83143 Giulio Benetti
2021-08-31 17:38 ` [Buildroot] [PATCH v2 2/2] package/ruby: fix build failure due to gcc bug 83143 Giulio Benetti
2021-09-11 16:20 ` [Buildroot] [PATCH v2 0/2] Add and workaround " Arnout Vandecappelle
2021-08-31 17:43 ` [Buildroot] [PATCH 1/2] toolchain: introduce BR2_TOOLCHAIN_HAS_GCC_BUG_83143 Giulio Benetti
2021-08-27 22:34 ` [Buildroot] [PATCH 2/2] package/ruby: fix build failure due to gcc bug 83143 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=20210830235951.24b82f6d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.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