Thread (11 messages) 11 messages, 2 authors, 2015-03-28

Re: [PATCH v3 2/2] selftests/powerpc: Add a test of the switch_endian() syscall

From: Michael Ellerman <mpe@ellerman.id.au>
Date: 2015-03-25 05:28:48

On Wed, 2015-03-18 at 16:04 +1100, Michael Ellerman wrote:
On Tue, 2015-03-17 at 11:35 +0530, Anshuman Khandual wrote:
quoted
On 03/17/2015 04:34 AM, Michael Ellerman wrote:
quoted
What are you seeing exactly?
I am running on a BE PKVM guest but compiling the test case on
a different BE machine which has newer version of the compiler.

cc (GCC) 4.8.3 20140624

cc -O2 -Wall -g -nostdlib -m64   -c -o check.o check.S
objcopy -j .text --reverse-bytes=4 -O binary check.o check-reversed.o
hexdump -v -e '/1 ".byte 0x%02X\n"' check-reversed.o > check-reversed.S
cc -O2 -Wall -g -nostdlib -m64    switch_endian_test.S check-reversed.S   -o switch_endian_test

which looks very similar to the details you have provided above.
Running on guest or host should not make any difference.
No it shouldn't.

Can you try strace, that should give you the full result code.

Also can you try gdb. You can't breakpoint in the wrong-endian region, but it
looks like you're getting through that anyway.

So try setting a breakpoint at line ~77, and you should be back in BE. Then you
can single step and see where it errors out.
Did you try these?

I want to merge this, and it works for me, but I'd be interested if you can
track down why it's failing for you.

cheers
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help