From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain-wrapper: do not use deprecated -mfused-madd
Date: Fri, 11 Aug 2017 08:08:58 +0200 [thread overview]
Message-ID: <20170811080858.336ba4d3@windsurf> (raw)
In-Reply-To: <20170811052847.GA32348@waldemar-brodkorb.de>
Hello,
On Fri, 11 Aug 2017 07:28:48 +0200, Waldemar Brodkorb wrote:
> GCC deprecated -mfused-madd, -ffp-contract=off should
> be used for Xburst workaround.
> uClibc compilations will fail, because a gcc warning
> is emitted while checking for TLS support in the compiler.
In which gcc version was -ffp-contract=off added ? Can we use that
unconditionally, or is it only available in recent gcc versions ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-11 6:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 5:28 [Buildroot] [PATCH] toolchain-wrapper: do not use deprecated -mfused-madd Waldemar Brodkorb
2017-08-11 6:08 ` Thomas Petazzoni [this message]
2017-08-11 9:53 ` Arnout Vandecappelle
2017-08-11 18:11 ` Waldemar Brodkorb
2017-08-11 20:54 ` Arnout Vandecappelle
2017-08-11 17:32 ` Waldemar Brodkorb
2017-08-11 21:00 ` Arnout Vandecappelle
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=20170811080858.336ba4d3@windsurf \
--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