From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Report from the Buildroot Meeting in Berlin
Date: Mon, 24 Oct 2016 14:02:51 +0200 [thread overview]
Message-ID: <874m42lztg.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <c2da1832-3282-33f0-1588-e828f3df4801@mind.be> (Arnout Vandecappelle's message of "Thu, 20 Oct 2016 18:39:37 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
>> * TARGET_CFLAGS = $(TARGET_WRAPPER_CFLAGS) $(TARGET_OPTIMIZATION) \
>> $(TARGET_DEBUGGING)
>> TARGET_CXXFLAGS = $(TARGET_CFLAGS)
>> TARGET_LDFLAGS = $(TARGET_CFLAGS)
>> TARGET_FCFLAGS = $(TARGET_CFLAGS)
> Turns out that it will be slightly more complicated than this. For MIPS, the
> -mmsa option to enable SIMD processing MUST NOT be used in kernel and bootloader
> builds. Therefore we cannot add it to TARGET_WRAPPER_CFLAGS. Instead, we'll have
> a TARGET_EXTRA_CFLAGS that does not get added to the wrapper but does get added
> to TARGET_CFLAGS and therefore passed to package buidls.
If that is the only problem, couldn't we just add -mno-msa to the
kernel/bootloader if _MIPS_MSA is enabled?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-10-24 12:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 20:10 [Buildroot] Report from the Buildroot Meeting in Berlin Thomas Petazzoni
2016-10-20 16:39 ` Arnout Vandecappelle
2016-10-21 8:25 ` Thomas Petazzoni
2016-10-21 8:57 ` Arnout Vandecappelle
2016-10-21 9:05 ` Thomas Petazzoni
2016-10-24 12:02 ` Peter Korsgaard [this message]
2016-10-24 12:19 ` Vicente Olivert Riera
2016-10-24 12:28 ` Thomas Petazzoni
2016-10-24 13:05 ` Arnout Vandecappelle
2016-10-24 14:52 ` Vicente Olivert Riera
2016-10-24 14:57 ` Thomas Petazzoni
2016-10-24 15:47 ` [Buildroot] Toolchain wrapper CFLAGS [was: Re: Report from the Buildroot Meeting in Berlin] Arnout Vandecappelle
2016-10-24 12:39 ` [Buildroot] Report from the Buildroot Meeting in Berlin Peter Korsgaard
2016-10-24 0:54 ` Sam Bobroff
2016-10-24 7:25 ` Thomas Petazzoni
2016-10-25 2:21 ` Sam Bobroff
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=874m42lztg.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.