[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
x86_64 specific tests in dwz vs. other architectures
- To: dwz@sourceware.org
- Subject: x86_64 specific tests in dwz vs. other architectures
- From: Jakub Jelinek <jakub@redhat.com>
- Date: Wed, 11 Dec 2019 17:46:21 +0100
- Authentication-results: sourceware.org; auth=none
- Delivered-to: listarch-dwz@sourceware.org
- Delivered-to: mailing list dwz@sourceware.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1576082788; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=tgKbxBJ2NVdVWZa6zGc+93ChaYPvapC1U9dUASaugFw=; b=MYJEPFIlY9s4EJEsp/7S8Ezp+U5+QxRnLEb0ZxycbjSCjXOI4mWFECpWd5J62Uih7pOBds izVqCzCpzQcG/MheHgE7v0yBIbyakGYGjKFsXKj2c8JVaxsJV5EbxZW+AYKfsWkkpU5PtS V4P58tPgYPIFES0Iw3YYOix4NKVpBSI=
- List-help: <mailto:dwz-help@sourceware.org>
- List-id: <dwz.sourceware.org>
- List-post: <mailto:dwz@sourceware.org>
- List-subscribe: <mailto:dwz-subscribe@sourceware.org>
- Mailing-list: contact dwz-help@sourceware.org; run by ezmlm
- Reply-to: Jakub Jelinek <jakub@redhat.com>
- Sender: dwz-owner@sourceware.org
- User-agent: Mutt/1.11.3 (2019-02-01)
Hi!
I've only got now to try building dwz 0.13 (just a scratch build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=39485926
) in Fedora, but looking at the build files, I see on non-x86_64
arches ugly messages like:
dw2-restrict.c: Assembler messages:
dw2-restrict.c:55: Error: unrecognized opcode: `movq'
dw2-restrict.c:58: Error: unrecognized opcode: `movq'
dw2-restrict.c:59: Error: unrecognized opcode: `movsbl'
dw2-restrict.c:60: Error: unrecognized opcode: `ret'
dw2-restrict.c:76: Error: unrecognized opcode: `pushq'
dw2-restrict.c:78: Error: unrecognized opcode: `movq'
dw2-restrict.c:80: Error: unrecognized opcode: `subq'
dw2-restrict.c:82: Error: unrecognized opcode: `leaq'
dw2-restrict.c:83: Error: unrecognized opcode: `movl'
dw2-restrict.c:86: Error: unrecognized opcode: `callq'
dw2-restrict.c:87: Error: unrecognized opcode: `addq'
dw2-restrict.c:88: Error: unrecognized opcode: `popq'
dw2-restrict.c:89: Error: unrecognized opcode: `ret'
on ppc64le,
dw2-restrict.c: Assembler messages:
dw2-restrict.c:55: Error: bad register name `%rdi'
dw2-restrict.c:58: Error: bad register name `%rsp)'
dw2-restrict.c:59: Error: bad register name `%rdi)'
dw2-restrict.c:76: Error: bad register name `%rbp'
dw2-restrict.c:78: Error: bad register name `%rsp'
dw2-restrict.c:80: Error: bad register name `%rsp'
dw2-restrict.c:82: Error: bad register name `%rdi'
dw2-restrict.c:83: Error: bad register name `%rbp)'
dw2-restrict.c:86: Error: invalid instruction suffix for `call'
dw2-restrict.c:87: Error: bad register name `%rsp'
dw2-restrict.c:88: Error: bad register name `%rbp'
...
/builddir/build/BUILD/dwz/testsuite/dwz.tests/dw2-skip-prologue.S:309: Error: cannot represent relocation type BFD_RELOC_64
as: /tmp/ccg3sw27.o: unsupported relocation type: 0x1
on i686 etc. Can't we ensure that the tests are assembled only on the
corresponding architecture and nowhere else if they are architecture
specific?
It is fine if some tests are UNSUPPORTED, just we should completely skip
them if they can't be assembled.
Jakub