From: Richard Henderson <richard.henderson@linaro.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg/ppc: Add vector opcodes
Date: Wed, 27 Feb 2019 21:11:48 -0800 [thread overview]
Message-ID: <dbae6af0-71a3-12b0-5a06-83a0bbb2c68a@linaro.org> (raw)
In-Reply-To: <20190228040157.GD27799@umbus.fritz.box>
On 2/27/19 8:01 PM, David Gibson wrote:
> On Wed, Feb 27, 2019 at 04:47:30PM -0800, Richard Henderson wrote:
>> On 2/24/19 3:31 PM, David Gibson wrote:
>>> I have access to POWER8 and POWER9 machines, but I haven't worked with
>>> RISU before. If you can give me a straightforward recipe I can try
>>> running the tests.
>>
>> From
>>
>> https://git.linaro.org/people/peter.maydell/risu.git
>
> And I assume build it, at which point I hit this:
>
> $ make
> gcc -Wall -D_GNU_SOURCE -DARCH=ppc64 -I /home/dwg/risu/risu -g -o risu_ppc64.o -c risu_ppc64.c
> risu_ppc64.c: In function ‘advance_pc’:
> risu_ppc64.c:19:25: error: dereferencing pointer to incomplete type ‘struct pt_regs’
> uc->uc_mcontext.regs->nip += 4;
> ^~
> make: *** [Makefile:44: risu_ppc64.o] Error 1
Dunno. Works for me.
$ uname -a
Linux gcc135.osuosl.org 4.14.0-115.2.2.el7a.ppc64le #1 SMP Wed Nov 28 21:39:33
GMT 2018 ppc64le ppc64le ppc64le GNU/Linux
$ head -2 /etc/os-release
NAME="CentOS Linux"
VERSION="7 (AltArch)"
I guess you'll need to debug this in your environment to find out what's different?
r~
next prev parent reply other threads:[~2019-02-28 5:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 5:59 [Qemu-devel] [PATCH] tcg/ppc: Add vector opcodes Richard Henderson
2019-02-22 17:13 ` Mark Cave-Ayland
2019-02-22 20:20 ` Richard Henderson
2019-02-24 23:31 ` David Gibson
2019-02-28 0:47 ` Richard Henderson
2019-02-28 4:01 ` David Gibson
2019-02-28 5:11 ` Richard Henderson [this message]
2019-02-27 15:45 ` no-reply
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=dbae6af0-71a3-12b0-5a06-83a0bbb2c68a@linaro.org \
--to=richard.henderson@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).