From: Joseph Myers <joseph@codesourcery.com>
To: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
Cc: Rogerio Alves <rcardoso@linux.ibm.com>,
"Gabriel F. T. Gomes" <gabriel@inconstante.eti.br>,
Florian Weimer <fweimer@redhat.com>, <libc-alpha@sourceware.org>
Subject: Re: [PATCH] power: Fix VSCR position on ucontext
Date: Fri, 11 Jan 2019 23:49:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1901112347220.10344@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87ef9j55vf.fsf@linux.ibm.com>
I'm seeing the test fail to build for powerpc64-linux-gnu (big-endian)
with my build-many-glibcs.py bots. (That's at least with GCC 7 and GCC 8;
my GCC mainline bot hasn't yet run after that commit.)
../sysdeps/powerpc/powerpc64/tst-ucontext-ppc64-vscr.c: In function 'do_test':
../sysdeps/powerpc/powerpc64/tst-ucontext-ppc64-vscr.c:51:3: error: inconsistent operand constraints in an 'asm'
asm volatile (".machine push;\n"
^~~
/scratch/jmyers/glibc-bot/build/glibcs/powerpc64-linux-gnu/glibc/sysd-rules:933: recipe for target '/scratch/jmyers/glibc-bot/build/glibcs/powerpc64-linux-gnu/glibc/stdlib/tst-ucontext-ppc64-vscr.o' failed
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-01-11 23:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 16:14 Rogerio Alves
2018-11-14 18:00 ` Florian Weimer
2018-11-16 13:18 ` Gabriel F. T. Gomes
2018-12-07 18:28 ` Rogerio Alves
2018-12-07 19:23 ` Gabriel F. T. Gomes
2018-12-10 17:18 ` Tulio Magno Quites Machado Filho
2018-12-10 18:12 ` Gabriel F. T. Gomes
2018-12-10 18:08 ` Gabriel F. T. Gomes
2018-12-10 18:25 ` Rogerio Alves
2018-12-10 21:20 ` Tulio Magno Quites Machado Filho
2018-12-19 19:30 ` Rogerio Alves
2019-01-10 19:52 ` Tulio Magno Quites Machado Filho
2019-01-11 12:01 ` Szabolcs Nagy
2019-01-11 12:15 ` Tulio Magno Quites Machado Filho
2019-01-11 19:52 ` Tulio Magno Quites Machado Filho
2019-01-11 23:49 ` Joseph Myers [this message]
2019-01-12 0:50 ` Tulio Magno Quites Machado Filho
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=alpine.DEB.2.21.1901112347220.10344@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=fweimer@redhat.com \
--cc=gabriel@inconstante.eti.br \
--cc=libc-alpha@sourceware.org \
--cc=rcardoso@linux.ibm.com \
--cc=tuliom@ascii.art.br \
/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).