From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] valgrind: disable for MIPS soft-float when using binutils >= 2.25
Date: Tue, 15 Mar 2016 14:37:49 +0100 [thread overview]
Message-ID: <20160315143749.0b6d5fb6@free-electrons.com> (raw)
In-Reply-To: <1458041310-65003-2-git-send-email-Vincent.Riera@imgtec.com>
Dear Vicente Olivert Riera,
On Tue, 15 Mar 2016 11:28:30 +0000, Vicente Olivert Riera wrote:
> As stated here [1], recent changes on the MIPS binutils sources have
> made it necessary for GCC to pass the -msoft-float to the assembler. Due
> to that, valgrind fails to build for MIPS soft-float when using a
> version of GCC >= 4.9 and binutils >= 2.25 because its using some
> hard-float instructions.
So I think we should just add "depends on !BR2_MIPS_SOFT_FLOAT.
If your use case is broken with the more recent versions of the tools,
and will continue to be broken for the newer versions of them, we
should IMO just disable completely the support on MIPS soft-float.
Of course, that's my own opinion, others might disagree.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-15 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 11:28 [Buildroot] [PATCH 1/2] Disable gcc-4.8.x + binutils-2.26 + MIPS combination Vicente Olivert Riera
2016-03-15 11:28 ` [Buildroot] [PATCH 2/2] valgrind: disable for MIPS soft-float when using binutils >= 2.25 Vicente Olivert Riera
2016-03-15 13:37 ` Thomas Petazzoni [this message]
2016-03-15 14:47 ` Waldemar Brodkorb
2016-04-04 15:21 ` Waldemar Brodkorb
2016-03-15 13:36 ` [Buildroot] [PATCH 1/2] Disable gcc-4.8.x + binutils-2.26 + MIPS combination Thomas Petazzoni
2016-03-15 13:55 ` Vicente Olivert Riera
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=20160315143749.0b6d5fb6@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