All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <manuel.lauss@gmail.com>,
	"Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: [RFC PATCH V2] MIPS: fix build with binutils 2.24.51+
Date: Mon, 25 Aug 2014 14:51:07 +0200	[thread overview]
Message-ID: <20140825125107.GA25892@linux-mips.org> (raw)
In-Reply-To: <1408465632-34262-1-git-send-email-manuel.lauss@gmail.com>

On Tue, Aug 19, 2014 at 06:27:12PM +0200, Manuel Lauss wrote:

> With binutils snapshots since 29.07.2014 I get the following build failure:
> {standard input}: Warning: .gnu_attribute 4,3 requires `softfloat'
>   LD      arch/mips/alchemy/common/built-in.o
> mipsel-softfloat-linux-gnu-ld: Warning: arch/mips/alchemy/common/built-in.o
>  uses -msoft-float (set by arch/mips/alchemy/common/prom.o),
>  arch/mips/alchemy/common/sleeper.o uses -mhard-float
> 
> Extend cflags with a soft-float directive for the assembler, and add
> hardfloat directives to assembler files dealing with FPU
> registers to compensate.

I had a discussion about this with Maciej.  He suggested that this
behavious of binutils should be taken a look at but also that we rather
should remove the -msoft-float option from the kernel and I support his
view.

I did add -msoft-float in 6218cf4410cfce7bc7e89834e73525b124625d4c
[[MIPS] Always pass -msoft-float.] in 2006 because back then there was a
wave of bug reports from people attempting to use hard fp in the kernel
which of course did result in FPR corruption.  Adding -msoft-float made
sure that floating point operations would result in a link error because
the kernel does not supply a soft-fp library.

But maybe there are other methods to achieve the same - such as

#define float diediedie
#define double goboom

  Ralf

  reply	other threads:[~2014-08-25 12:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 16:27 [RFC PATCH V2] MIPS: fix build with binutils 2.24.51+ Manuel Lauss
2014-08-25 12:51 ` Ralf Baechle [this message]
2014-08-25 14:27   ` Maciej W. Rozycki
2014-08-25 19:29     ` Manuel Lauss
2014-08-25 19:57       ` Ralf Baechle
2014-08-25 19:57       ` Maciej W. Rozycki
2014-08-26 10:45         ` Matthew Fortune
2014-08-26 10:45           ` Matthew Fortune
2014-10-10 14:39       ` Markos Chandras
2014-10-10 14:39         ` Markos Chandras
2014-10-10 14:40         ` Markos Chandras
2014-10-10 14:40           ` Markos Chandras
2014-10-11  6:53           ` Manuel Lauss

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=20140825125107.GA25892@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=manuel.lauss@gmail.com \
    /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.