From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: buildroot@buildroot.org
Cc: Asaf Kahlon <asafka7@gmail.com>,
Romain Naour <romain.naour@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Subject: Re: [Buildroot] [PATCH 1/2] toolchain: introduce BR2_TOOLCHAIN_HAS_GCC_BUG_102472
Date: Fri, 24 Sep 2021 23:27:04 +0200 [thread overview]
Message-ID: <0a3bb8bf-27b6-8ee5-7b4e-a57169c7f18e@benettiengineering.com> (raw)
In-Reply-To: <20210923164553.1218801-1-giulio.benetti@benettiengineering.com>
Hi All,
On 9/23/21 6:45 PM, Giulio Benetti wrote:
> python-uvloop package hang while building for the m68k architecture with
> optimization enabled with gcc = 11.2.0:
> http://autobuild.buildroot.net/results/17d/17d6e6422abadcd6313c430c40f2a5d7162dbbd3/
Here it's not true. I've found out that it doesn't really time out, it
only takes a lot to build with optimization enabled since loop.c file is
7Mb big. So please drop this patch and the next one. I've marked them
both as rejected in patchwork already.
Sorry for the noise!
Kind regards
--
Giulio Benetti
Benetti Engineering sas
> It's been reported upstream:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102472
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
> toolchain/Config.in | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/toolchain/Config.in b/toolchain/Config.in
> index 8b01067105..adb4d63759 100644
> --- a/toolchain/Config.in
> +++ b/toolchain/Config.in
> @@ -210,6 +210,13 @@ config BR2_TOOLCHAIN_HAS_GCC_BUG_101952
> bool
> default y if BR2_sh4
>
> +# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102472
> +# ICE: on m68k it enters an infinite loop
> +# This bug still exists in gcc = 11.2.0
> +config BR2_TOOLCHAIN_HAS_GCC_BUG_102472
> + bool
> + default y if BR2_m68k
> +
> config BR2_TOOLCHAIN_HAS_NATIVE_RPC
> bool
>
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-09-24 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 16:45 [Buildroot] [PATCH 1/2] toolchain: introduce BR2_TOOLCHAIN_HAS_GCC_BUG_102472 Giulio Benetti
2021-09-23 16:45 ` [Buildroot] [PATCH 2/2] package/python-uvloop: work-around m68k toolchain infinite loop Giulio Benetti
2021-09-24 21:27 ` Giulio Benetti [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=0a3bb8bf-27b6-8ee5-7b4e-a57169c7f18e@benettiengineering.com \
--to=giulio.benetti@benettiengineering.com \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.com \
--cc=thomas.petazzoni@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).