From: Ulrich Hecht <uli@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] s390 host support
Date: Tue, 13 Nov 2007 15:05:25 +0100 [thread overview]
Message-ID: <200711131505.26871.uli@suse.de> (raw)
In-Reply-To: <20071113130052.GA22061@wavehammer.waldi.eu.org>
On Tuesday 13 November 2007, Bastian Blank wrote:
> Please describe the environment you work in, including compiler
> versions and patchsets.
gcc 3.3 (Hammer branch, really vintage stuff) with recent (2.18.50)
binutils. We already use gcc 4 for targets where the old one won't work
(ia64 and ppc64); maybe we should do so for s390 as well.
> The jcc fix looks like a workaround for an undescribed problem. Please
> describe this. Hmm, the comments say "for unknown reasons".
I am actually suspecting this to be a compiler bug, but I did not
investigate it further once I found that disabling it helps.
CU
Uli
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2007-11-13 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 20:42 [Qemu-devel] s390 host support Bastian Blank
2007-11-12 17:14 ` Ulrich Hecht
2007-11-13 13:00 ` Bastian Blank
2007-11-13 14:05 ` Ulrich Hecht [this message]
2007-11-13 17:20 ` Bastian Blank
2007-11-16 19:09 ` [Qemu-devel] " Bastian Blank
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=200711131505.26871.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 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).