From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Richard Henderson <richard.henderson@linaro.org>,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH] tests/tcg/s390x: Use a different PCRel32 notation in branch-relative-long.c
Date: Wed, 04 May 2022 11:07:55 +0200 [thread overview]
Message-ID: <1c4e55e45a92250f93d7671b4f658e616fc1edce.camel@linux.ibm.com> (raw)
In-Reply-To: <f7a77dcc-590c-96f5-8e92-5806f51ac0d4@redhat.com>
On Wed, 2022-05-04 at 09:01 +0200, Thomas Huth wrote:
> On 04/05/2022 00.46, Ilya Leoshkevich wrote:
> > On Tue, 2022-05-03 at 21:26 +0200, Thomas Huth wrote:
> > > On 03/05/2022 11.02, Thomas Huth wrote:
> > > > On 02/05/2022 18.48, Ilya Leoshkevich wrote:
> > > > > Binutils >=2.37 and Clang do not accept (. - 0x100000000)
> > > > > PCRel32
> > > > > constants. While this looks like a bug that needs fixing, use
> > > > > a
> > > > > different notation (-0x100000000) as a workaround.
> > > > >
> > > > > Reported-by: Thomas Huth <thuth@redhat.com>
> > > > > Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> > > > > ---
> > > > > tests/tcg/s390x/branch-relative-long.c | 4 ++--
> > > > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > > > >
> > > > > diff --git a/tests/tcg/s390x/branch-relative-long.c
> > > > > b/tests/tcg/s390x/branch-relative-long.c
> > > > > index 94219afcad..8ce9f1c2e5 100644
> > > > > --- a/tests/tcg/s390x/branch-relative-long.c
> > > > > +++ b/tests/tcg/s390x/branch-relative-long.c
> > > > > @@ -13,8 +13,8 @@
> > > > > #_name "_end:\n");
> > > > > DEFINE_ASM(br_r14, "br %r14");
> > > > > -DEFINE_ASM(brasl_r0, "brasl %r0,.-0x100000000");
> > > > > -DEFINE_ASM(brcl_0xf, "brcl 0xf,.-0x100000000");
> > > > > +DEFINE_ASM(brasl_r0, "brasl %r0,-0x100000000");
> > > > > +DEFINE_ASM(brcl_0xf, "brcl 0xf,-0x100000000");
> > > >
> > > > Works for me, thanks!
> > >
> > > Sorry, I spoke too soon - it compiles fine, and also runs fine
> > > when I
> > > run it
> > > natively, but when I run it through "qemu-s390x", it crashes...
> > > does
> > > that
> > > work for you?
> >
> > Hi, yes, I just double-checked - it works fine for me.
> > Could you please share the resulting test binary?
>
>
> Sure, here it is:
>
> https://people.redhat.com/~thuth/data/branch-relative-long
>
> Thomas
Your binary worked fine for me.
QEMU commit 2e3408b3cc7de4e87a9adafc8c19bfce3abec947,
x86_64 host,
configured with --target-list=s390x-linux-user.
next prev parent reply other threads:[~2022-05-04 9:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 16:48 [PATCH] tests/tcg/s390x: Use a different PCRel32 notation in branch-relative-long.c Ilya Leoshkevich
2022-05-03 9:02 ` Thomas Huth
2022-05-03 19:26 ` Thomas Huth
2022-05-03 22:46 ` Ilya Leoshkevich
2022-05-04 7:01 ` Thomas Huth
2022-05-04 9:07 ` Ilya Leoshkevich [this message]
2022-05-04 9:14 ` branch-relative-long fails on s390x host (was: [PATCH] tests/tcg/s390x: Use a different PCRel32 notation in branch-relative-long.c) Thomas Huth
2022-05-04 9:37 ` Ilya Leoshkevich
2022-05-04 10:46 ` Thomas Huth
2022-05-04 10:51 ` Ilya Leoshkevich
2022-05-04 11:24 ` Ilya Leoshkevich
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=1c4e55e45a92250f93d7671b4f658e616fc1edce.camel@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--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).