From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] MIPS: add support for XBurst cores
Date: Wed, 9 Nov 2016 21:37:40 +0100 [thread overview]
Message-ID: <20161109213740.3438b5d6@free-electrons.com> (raw)
In-Reply-To: <20161109161658.53527-1-Vincent.Riera@imgtec.com>
Hello,
On Wed, 9 Nov 2016 16:16:57 +0000, Vicente Olivert Riera wrote:
> The Ingenic XBurst is a MIPS32R2 microprocessor.
>
> It has a bug in the FPU that can generate incorrect results in certain
> cases. The problem shows up when you have several fused madd
> instructions in sequence with dependant operands.
>
> Using the -mno-fused-madd option prevents gcc from emitting these
> instructions. This patch adds changes to the toolchain wrapper to use
> that option.
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> Changes v2 -> v3:
> - Improve commit log and add help section. (Suggested by Arnout)
> Changes v1 -> v2:
> - Do not add -mmxu to the wrapper.
> ---
> arch/Config.in.mips | 14 ++++++++++++++
> toolchain/toolchain-wrapper.c | 3 +++
> toolchain/toolchain-wrapper.mk | 5 +++++
> 3 files changed, 22 insertions(+)
I've applied both patches to master. Even though it's adding a new
architecture entry, it's really a bug fix needed for the
ci20_defconfig, which is why I've chosen to apply this to master.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-09 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 16:16 [Buildroot] [PATCH v3 1/2] MIPS: add support for XBurst cores Vicente Olivert Riera
2016-11-09 16:16 ` [Buildroot] [PATCH v3 2/2] ci20_defconfig: use XBurst CPU Vicente Olivert Riera
2016-11-09 20:37 ` Thomas Petazzoni [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=20161109213740.3438b5d6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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