From: "Paul A. Clarke via Libc-alpha" <libc-alpha@sourceware.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>,
libc-alpha@sourceware.org
Subject: Re: [PATCH] powerpc: Fix unrecognized instruction errors with recent GCC
Date: Sat, 25 Sep 2021 10:09:09 -0500 [thread overview]
Message-ID: <20210925150909.GA334336@li-24c3614c-2adc-11b2-a85c-85f334518bdb.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2109221146170.29115@digraph.polyomino.org.uk>
On Wed, Sep 22, 2021 at 11:48:32AM +0000, Joseph Myers wrote:
> Even with this commit included, I'm still seeing such errors with
> build-many-glibcs.py for powerpc-linux-gnu, powerpc-linux-gnu-power4,
> powerpc-linux-gnu-soft and powerpc64-linux-gnu, which I expect have the
> same underlying cause.
>
> https://sourceware.org/pipermail/libc-testresults/2021q3/008589.html
>
> These are all errors building tst-set_ppr:
>
> /tmp/ccyn2EoO.s: Assembler messages:
> /tmp/ccyn2EoO.s:73: Error: unrecognized opcode: `mfppr32'
> /tmp/ccyn2EoO.s:130: Error: unrecognized opcode: `mfppr32'
> /tmp/ccyn2EoO.s:197: Error: unrecognized opcode: `mfppr32'
> /tmp/ccyn2EoO.s:288: Error: unrecognized opcode: `mfppr32'
> /tmp/ccyn2EoO.s:340: Error: unrecognized opcode: `mfppr32'
> /tmp/ccyn2EoO.s:420: Error: unrecognized opcode: `mfppr32'
> /scratch/jmyers/glibc-bot/build/glibcs/powerpc-linux-gnu/glibc/sysd-rules:723: recipe for target '/scratch/jmyers/glibc-bot/build/glibcs/powerpc-linux-gnu/glibc/misc/tst-set_ppr.o' failed
Thanks for the report, Joseph!
This manifests only with a very recent version of binutils (not even the
current release, 2.37). It is likely provoked by commit
b25f942e18d6ecd7ec3e2d2e9930eb4f996c258a "PowerPC: ignore sticky options
for .machine". (I think there is a fair amount of fallout from that
change.)
Interestingly, there was a change (9250e6610fdb0f3a6f238d2813e319a41fb7a810
"powerpc: Fix build failures with current GCC") back in 2019 to that test's
Makefile to add `-many` to the compile options for exactly this problem
when `-many` stopped being passed by GCC to the assembler. Now, even
passing `-many` on the command line doesn't work.
I'll post a fix to include the required `.machine` directives for that test
shortly.
PC
prev parent reply other threads:[~2021-09-25 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 18:19 [PATCH] powerpc: Fix unrecognized instruction errors with recent GCC Paul A. Clarke via Libc-alpha
2021-09-20 12:56 ` Tulio Magno Quites Machado Filho via Libc-alpha
2021-09-22 11:48 ` Joseph Myers
2021-09-25 15:09 ` Paul A. Clarke via Libc-alpha [this message]
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210925150909.GA334336@li-24c3614c-2adc-11b2-a85c-85f334518bdb.ibm.com \
--to=libc-alpha@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=pc@us.ibm.com \
--cc=tuliom@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).