From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#836741: linux: FTBFS on powerpcspe due to the use of unsupported instructions
Date: Mon, 05 Sep 2016 13:34:58 +0200 [thread overview]
Message-ID: <147307529891.26744.6537243126225612598.reportbug@ikarus> (raw)
Source: linux
Version: 4.7.2-1
Severity: normal
User: debian-powerpc@lists.debian.org
Usertags: powerpcspe
Hi!
Linux 4.7.x introduced another regression on powerpcspe due to the use of
unsupported assembly instructions [1]:
/<<PKGBUILDDIR>>/arch/powerpc/xmon/spr_access.S: Assembler messages:
/<<PKGBUILDDIR>>/arch/powerpc/xmon/spr_access.S:5: Error: unrecognized opcode: `ld'
/<<PKGBUILDDIR>>/arch/powerpc/xmon/spr_access.S:10: Error: unrecognized opcode: `ld'
/<<PKGBUILDDIR>>/scripts/Makefile.build:331: recipe for target 'arch/powerpc/xmon/spr_access.o' failed
make[6]: *** [arch/powerpc/xmon/spr_access.o] Error 1
This is very reminiscent of #823526 [2] which also used some FPU instructions
not available on powerpcspe/e500. And, indeed, like "ldarx" and "stdcx", "ld"
is not available on e500 either [3] (see p. 3-68).
I haven't looked at the code yet, but I assume guarding the code with some
additional #ifdef's should fix the issue the same way as in #823526.
Thanks,
Adrian
> [1] https://buildd.debian.org/status/fetch.php?pkg=linux&arch=powerpcspe&ver=4.7.2-1&stamp=1472977882
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823526
> [3] http://www.nxp.com/files/32bit/doc/ref_manual/E500CORERM.pdf
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
reply other threads:[~2016-09-05 11:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=147307529891.26744.6537243126225612598.reportbug@ikarus \
--to=glaubitz@physik.fu-berlin.de \
--cc=836741@bugs.debian.org \
--cc=submit@bugs.debian.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