Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 1 Oct 2020 10:06:16 +0200	[thread overview]
Message-ID: <20201001100616.2cb75cc9@windsurf.home> (raw)
In-Reply-To: <2efd6cda-edbf-bb5e-d7d7-89ca4491f0f0@gmail.com>

On Wed, 30 Sep 2020 23:04:22 +0200
Romain Naour <romain.naour@gmail.com> wrote:

> > The gotcha being of course that we don't pass TARGET_CFLAGS to the
> > Linux package...  
> 
> Indeed, I have no ideas if the userspace built with this toolchain is really
> working... except for busybox which was used by qemu_microblazeel_mmu_defconfig

I think we should be passing this flag in TARGET_CFLAGS. What bothers
me is that passing it in TARGET_CFLAGS would not resolve the Linux
build issue, as Linux isn't built with TARGET_CFLAGS...

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-10-01  8:06 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
2020-09-30 21:04     ` Romain Naour
2020-10-01  8:06       ` Thomas Petazzoni [this message]
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=20201001100616.2cb75cc9@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