public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65341] [5 Regression] glibc build failure on ppc64le: setcontext.S:367: Error: junk at end of line: `1,0'
Date: Sat, 07 Mar 2015 18:45:00 -0000 [thread overview]
Message-ID: <bug-65341-4-gPxHZe8xN8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65341-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65341
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
The four operand form of the mtfsf instruction was added in Power ISA 2.5 and
gas recognizes it when targeting power6 or later. From the glibc snippet it
does look like the first block controlled by _ARCH_PWR6 is missing the .machine
"power6" directive. Once it's added I would expect as to be happy again (it is
in my tests, though I didn't go as far as building all of glibc).
365 # ifdef _ARCH_PWR6
366 /* Use the extended four-operand version of the mtfsf insn. */
367 mtfsf 0xff,fp0,1,0
368 # else
369 .machine push
370 .machine "power6"
next prev parent reply other threads:[~2015-03-07 18:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 8:27 [Bug target/65341] New: " trippels at gcc dot gnu.org
2015-03-07 12:40 ` [Bug target/65341] " jakub at gcc dot gnu.org
2015-03-07 15:06 ` dje at gcc dot gnu.org
2015-03-07 17:34 ` trippels at gcc dot gnu.org
2015-03-07 18:45 ` msebor at gcc dot gnu.org [this message]
2015-03-07 19:02 ` jakub at gcc dot gnu.org
2015-03-07 19:28 ` msebor at gcc dot gnu.org
2015-03-07 19:36 ` dje at gcc dot gnu.org
2015-03-07 21:25 ` msebor at gcc dot gnu.org
2015-03-08 6:22 ` jakub at gcc dot gnu.org
2015-03-08 6:29 ` trippels at gcc dot gnu.org
2015-03-08 13:37 ` dje at gcc dot gnu.org
2015-03-08 14:06 ` trippels at gcc dot gnu.org
2015-03-08 16:16 ` msebor at gcc dot gnu.org
2015-03-09 1:37 ` dje at gcc dot gnu.org
2015-03-09 12:12 ` rguenth at gcc dot gnu.org
2015-03-09 16:13 ` meissner at gcc dot gnu.org
2015-03-09 16:45 ` trippels at gcc dot gnu.org
2015-03-26 1:26 ` pinskia at gcc dot gnu.org
2015-03-26 2:38 ` msebor at gcc dot gnu.org
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=bug-65341-4-gPxHZe8xN8@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).