From: Markos Chandras <Markos.Chandras@imgtec.com>
To: <linux-mips@linux-mips.org>
Subject: Re: compile failure linux 3.10 with gcc 4.9.3 for mips
Date: Wed, 15 Jul 2015 09:03:18 +0100 [thread overview]
Message-ID: <55A613C6.3040505@imgtec.com> (raw)
In-Reply-To: <CAAA5faEN3MmWACoT2g2+9aOj1C=vj7UcNxd3Lez_K4_sCS8jBQ@mail.gmail.com>
On 07/14/2015 07:04 PM, Reinoud Koornstra wrote:
> Hi Everyone,
>
> Did anybody enounter the following compiler problem with linux 3.10.81?
> gcc version is 4.9.3 for mips and binutils 2.25
>
> arch/mips/kernel/r4k_fpu.S: Assembler messages:
> arch/mips/kernel/r4k_fpu.S:59: Error: opcode not supported on this
> processor: mips3 (mips3) `sdc1 $f0,272+0($4)'
I think this is a known bug and it needs a backport of
https://patchwork.linux-mips.org/patch/8355/
--
markos
WARNING: multiple messages have this Message-ID (diff)
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: linux-mips@linux-mips.org
Subject: Re: compile failure linux 3.10 with gcc 4.9.3 for mips
Date: Wed, 15 Jul 2015 09:03:18 +0100 [thread overview]
Message-ID: <55A613C6.3040505@imgtec.com> (raw)
Message-ID: <20150715080318.vt-Fh4XkM_ESBlhOg_nMKFzmjPcum9mlBQMnCrJRWho@z> (raw)
In-Reply-To: <CAAA5faEN3MmWACoT2g2+9aOj1C=vj7UcNxd3Lez_K4_sCS8jBQ@mail.gmail.com>
On 07/14/2015 07:04 PM, Reinoud Koornstra wrote:
> Hi Everyone,
>
> Did anybody enounter the following compiler problem with linux 3.10.81?
> gcc version is 4.9.3 for mips and binutils 2.25
>
> arch/mips/kernel/r4k_fpu.S: Assembler messages:
> arch/mips/kernel/r4k_fpu.S:59: Error: opcode not supported on this
> processor: mips3 (mips3) `sdc1 $f0,272+0($4)'
I think this is a known bug and it needs a backport of
https://patchwork.linux-mips.org/patch/8355/
--
markos
next prev parent reply other threads:[~2015-07-15 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 18:04 compile failure linux 3.10 with gcc 4.9.3 for mips Reinoud Koornstra
2015-07-15 8:03 ` Markos Chandras [this message]
2015-07-15 8:03 ` Markos Chandras
2015-07-15 19:56 ` Reinoud Koornstra
2015-07-16 8:42 ` Markos Chandras
2015-07-16 8:42 ` Markos Chandras
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=55A613C6.3040505@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=linux-mips@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