From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] linux: Disable -ftree-loop-distribute-patterns when building for microblaze with gcc >= 10
Date: Wed, 30 Sep 2020 22:59:21 +0200 [thread overview]
Message-ID: <20200930225921.39dbe8a5@windsurf.home> (raw)
In-Reply-To: <20200926191330.96074-2-romain.naour@gmail.com>
On Sat, 26 Sep 2020 21:13:30 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> +# https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=5879ab5fafedc8f6f9bfe95a4cf8501b0df90edd
> +# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97208
> +ifeq ($(BR2_TOOLCHAIN_GCC_AT_LEAST_10)$(BR2_microblaze),yy)
> +LINUX_KCFLAGS += -fno-tree-loop-distribute-patterns
> +endif
I am wondering if this is the right approach. If the
-ftree-loop-distribute-patterns breaks stuff for the kernel, presumably
it could also break stuff for user-space software. So I guess we should
instead disable it entirely in TARGET_CFLAGS.
The gotcha being of course that we don't pass TARGET_CFLAGS to the
Linux package...
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-09-30 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 19:13 [Buildroot] [PATCH 1/2] linux: introduce LINUX_KCFLAGS to add additional options to the C compiler Romain Naour
2020-09-26 19:13 ` [Buildroot] [PATCH 2/2] linux: Disable -ftree-loop-distribute-patterns when building for microblaze with gcc >= 10 Romain Naour
2020-09-30 20:59 ` Thomas Petazzoni [this message]
2020-09-30 21:04 ` Romain Naour
2020-10-01 8:06 ` Thomas Petazzoni
2020-10-06 18:46 ` Arnout Vandecappelle
2020-10-06 18:50 ` 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=20200930225921.39dbe8a5@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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