From: Ulrich Hecht <uli@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] S/390 host fixed
Date: Wed, 1 Aug 2007 15:44:43 +0200 [thread overview]
Message-ID: <200708011544.43401.uli@suse.de> (raw)
In-Reply-To: <20070731235915.GL26960@networkno.de>
On Wednesday 01 August 2007 01:59, Thiemo Seufer wrote:
> > - AIOLIBS="-lrt"
> > + AIOLIBS="-lrt -lpthread"
>
> Why is this needed? Linux toolchains should add -lpthread implicitly.
Our SLES9 toolchain seems not to. It's a near-cosmetic change.
> > +#ifdef __s390__
> > + retaddr = (void*)((unsigned long)retaddr & 0x7fffffffUL);
> > +#endif
>
> All of those look weird. Is this a null-extension vs. sign-extension
> issue?
S/390 has a 31 (thirty-one) bit address space; the MSB of the PSW is not
part of the address and must be masked out. This is simply part of the
architecture, there's no way around it.
> > +#ifdef __s390__
> > + func = NULL; /* does not work on S/390 for unknown
> > reasons */ +#else
> > func = gen_jcc_sub[s->cc_op - CC_OP_SUBB][jcc_op];
> > +#endif
>
> Hum. It wold be good to know what happens here.
Indeed. :)
> > +#ifdef __s390__
> > + if(!T1)
> > + T0 = (int32_t)env->fcr0;
> > + else if(T1 == 25)
[...]
>
> I guess this breaks when you _breathe_ at the compiler.
Probably, but that is true for a significant part of the QEMU codebase...
CU
Uli
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2007-08-01 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 11:49 [Qemu-devel] [PATCH] S/390 host fixed Ulrich Hecht
2007-07-30 12:37 ` Sunil Amitkumar Janki
2007-07-30 14:05 ` Ulrich Hecht
2007-07-31 23:59 ` Thiemo Seufer
2007-08-01 1:02 ` Paul Brook
2007-08-01 13:58 ` Dan Shearer
2007-08-01 14:23 ` [Qemu-devel] replacing dyngen (was: S/390 host fixed) Paul Brook
2007-08-01 14:31 ` Dan Shearer
2007-08-01 14:47 ` Paul Brook
2007-08-01 13:44 ` Ulrich Hecht [this message]
2007-09-13 4:21 ` [Qemu-devel] [PATCH] S/390 host fixed Thiemo Seufer
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=200708011544.43401.uli@suse.de \
--to=uli@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.