Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Matthew Fortune <Matthew.Fortune@imgtec.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Manuel Lauss <manuel.lauss@gmail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>,
	"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [RFC PATCH v6] MIPS: fix build with binutils 2.24.51+
Date: Fri, 7 Nov 2014 11:32:05 +0000	[thread overview]
Message-ID: <545CADB5.3050703@imgtec.com> (raw)
In-Reply-To: <6D39441BF12EF246A7ABCE6654B0235320F6C533@LEMAIL01.le.imgtec.org>

On 11/07/2014 11:05 AM, Matthew Fortune wrote:
>> +(mips1) `cfc1 $2,$31'
>> make[1]: *** [arch/mips/math-emu/cp1emu.o] Error 1
>> make: *** [arch/mips/math-emu] Error 2
>> make: *** Waiting for unfinished jobs....
> 
> This is the offending code in cp1emu.c:
> 
>                         if (is_fpu_owner())
>                                 asm volatile(
>                                         ".set push\n"
>                                         "\t.set mips1\n"
>                                         "\tcfc1\t%0,$31\n"
>                                         "\t.set pop" : "=r" (fcr31));
>                         else
>                                 fcr31 = current->thread.fpu.fcr31;
>                         preempt_enable();
> 
> I'm not sure how this can have built with binutils 2.23 (as indicated by
> Manuel and not built with 2.24). The reason this works with the latest
> version of binutils 2.24.x is that cfc1 has been reclassified as not an
> FPU instruction.
> 
> This just needs the hardfloat annotation adding via the macro as in the
> other cases.
> 
> Thanks,
> Matthew
> 
I am confused about this comment. The problem is reproducible with the
latest Mentor toolchain which uses the following gas
GNU assembler version 2.24.51 (mips-linux-gnu) using BFD version
(Sourcery CodeBench Lite 2014.05-27) 2.24.51.20140217.

I am not sure how Manuel's patch triggered this problem on Mentor to be
honest.

-- 
markos

  reply	other threads:[~2014-11-07 11:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 16:03 [RFC PATCH v6] MIPS: fix build with binutils 2.24.51+ Manuel Lauss
2014-10-31 16:13 ` Markos Chandras
2014-10-31 16:22   ` Manuel Lauss
2014-11-05 16:22     ` Matthew Fortune
2014-10-31 16:35   ` Matthew Fortune
2014-11-07  2:02 ` Ralf Baechle
2014-11-07 11:05   ` Matthew Fortune
2014-11-07 11:32     ` Markos Chandras [this message]
2014-11-07 12:28     ` 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=545CADB5.3050703@imgtec.com \
    --to=markos.chandras@imgtec.com \
    --cc=Matthew.Fortune@imgtec.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=manuel.lauss@gmail.com \
    --cc=ralf@linux-mips.org \
    /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