qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Thomas Huth <thuth@redhat.com>, Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] Provide safe_syscall for s390x
Date: Mon, 17 Oct 2016 12:55:59 +0200	[thread overview]
Message-ID: <13e93e4f-97f1-d088-a170-2c0400b57175@de.ibm.com> (raw)
In-Reply-To: <44ae9753-110b-4419-5734-66c3b1d0f9a4@redhat.com>

On 10/17/2016 10:26 AM, Thomas Huth wrote:
> On 14.10.2016 20:58, Michael Tokarev wrote:
>> Hi.
>>
>> This commit: c9bc3437a905b660561a26cd4ecc64579843267b
>> Author: Richard Henderson <rth@twiddle.net>
>> Date:   Tue Jun 21 17:32:12 2016 -0700
>>
>>     linux-user: Provide safe_syscall for s390x
>>
>> does not build on debian unstable porterbox for s390x, with
>> the following error message:
>>
>> linux-user/host/s390x/safe-syscall.inc.S: Assembler messages:
>> linux-user/host/s390x/safe-syscall.inc.S:75: Error: Unrecognized opcode:
>> `lt'
>> rules.mak:72: recipe for target 'linux-user/safe-syscall.o' failed
>>
>> Since I know nothing about s390, I've no idea what's at fault
>> here... :)  Thought I'd report this :)
> 
> "lt" seems to be a newer s390x opcode which has been added to the
> architecture within the last ten years or so. So maybe you've got to add
> some "-march=xxx" flag when compiling this file?
> Could you maybe start with finding out the exact comand line that is
> used to compile this file?

Yes, lt was added with the extended immidiate facility. So either use -march=z9-109 (introduced in
2005) or replace the lt with an l + ltr to also run on older models.

  parent reply	other threads:[~2016-10-17 10:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 18:58 [Qemu-devel] Provide safe_syscall for s390x Michael Tokarev
2016-10-17  8:26 ` Thomas Huth
2016-10-17 10:39   ` Michael Tokarev
2016-10-17 10:49     ` Michael Tokarev
2016-10-17 10:53       ` Thomas Huth
2016-10-17 10:55         ` Michael Tokarev
2016-10-17 10:54       ` Michael Tokarev
2016-10-17 10:55   ` Christian Borntraeger [this message]
2016-10-17 14:35     ` Richard Henderson
2016-10-18 22:17       ` Aurelien Jarno
2016-10-19 17:24         ` Richard Henderson
2016-10-26 17:10           ` Michael Tokarev

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=13e93e4f-97f1-d088-a170-2c0400b57175@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.com \
    /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).