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 21:25:00 -0000 [thread overview]
Message-ID: <bug-65341-4-cHRAP6zlhH@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
--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
(In reply to David Edelsohn from comment #7)
I assume the patch you are referring to is r221132 (pr65138). It doesn't look
like that's fixed it. The latest trunk exhibits the same problem:
$ cat t.s && /build/gcc-trunk-git/gcc/xgcc -B /build/gcc-trunk-git/gcc -dM -E
-xc - < /dev/null | grep PWR6 && /build/gcc-trunk-git/gcc/xgcc -B
/build/gcc-trunk-git/gcc -c -v t.s
.text
start:
mtfsf 6,10,0,0
#define _ARCH_PWR6 1
Reading specs from /build/gcc-trunk-git/gcc/specs
COLLECT_GCC=/build/gcc-trunk-git/gcc/xgcc
Target: powerpc64le-unknown-linux-gnu
Configured with: /src/gcc-trunk-git/configure --disable-bootstrap
--enable-languages=c,c++
Thread model: posix
gcc version 5.0.0 20150307 (experimental) (GCC)
COLLECT_GCC_OPTIONS='-B' '/build/gcc-trunk-git/gcc' '-c' '-v'
/build/gcc-trunk-git/gcc/as -v -a64 -mppc64 -many -mlittle -o t.o t.s
GNU assembler version 2.23.52.0.1 (ppc64le-redhat-linux) using BFD version
version 2.23.52.0.1-30.ael7b 20130226
t.s: Assembler messages:
t.s:3: Error: junk at end of line: `0,0'
next prev parent reply other threads:[~2015-03-07 21:25 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
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 [this message]
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-cHRAP6zlhH@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).