From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ci20_defconfig: disable madd instructions to avoid FPU bug
Date: Wed, 19 Oct 2016 11:31:54 +0200 [thread overview]
Message-ID: <87a8e0elbp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <68e76d80-a505-e029-941a-fe43d9780536@imgtec.com> (Vicente Olivert Riera's message of "Wed, 19 Oct 2016 09:47:03 +0100")
>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes:
Hi,
>> Note: this is *really* a question. I am not sure we want to make such a
>> change to the MIPS CPU selection.
> We could add an Ingenic XBurst entry in the MIPS CPU selection, and then
> add that -mno-fused-madd option to the wrapper based on that selection.
> If you are OK with that, please let me know and I'll cook the patch.
Yes, I believe this is the way we want to move forward.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-10-19 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 12:24 [Buildroot] [PATCH] ci20_defconfig: disable madd instructions to avoid FPU bug Vicente Olivert Riera
2016-10-18 12:54 ` Thomas Petazzoni
2016-10-19 8:47 ` Vicente Olivert Riera
2016-10-19 9:31 ` Peter Korsgaard [this message]
2016-10-19 9:32 ` Thomas Petazzoni
2016-10-19 10:19 ` Vicente Olivert Riera
2016-10-21 19:45 ` Arnout Vandecappelle
2016-10-22 12:08 ` 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=87a8e0elbp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox