qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu dyngen.c exec-i386.c exec-i386.h exec.h op...
Date: 04 Jun 2003 14:12:02 +0200	[thread overview]
Message-ID: <87adcym48d.fsf@student.uni-tuebingen.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0306041142590.1531-100000@Tempo.Update.UU.SE>

Jerker Nyberg <jerker@update.uu.se> writes:

> I tried to compile qemu on Alpha but cannot get it to work. I use
> gcc-2.96-112.7.1 (?) on a Red Hat Linux 7.1 distribution with
> kernel-2.4.3.
> 
> I removed the "CFLAGS += -msmall-data -msmall-text" to get the
> compilation going, but got stuck later again at "./dyngen -o
> op-i386.h op-i386.o" with "dyngen: ret expected at the end of
> op_raise_interrupt".

Hmm, very weird. Must be a quirk of your compiler, maybe it doesn't
understand -fno-reorder-blocks -fno-optimize-sibling-calls
properly. 2.96 is pretty ancient and not even an official gcc release,
so I am not sure anybody is interested in making qemu work with
it. I'd advise to upgrade to 3.3.

Also, kernel 2.4.3 doesn not support getting the fault address in a
signal handler (unless Red Hat patched that in). I don't know how
essential that is for qemu, though.

Finally, qemu does currently not work on Alpha anyway, and only worked
for very simple programs previously, maybe Fabrice will have a look at
it, I don't have time currently, unfortunately.

-- 
	Falk

      reply	other threads:[~2003-06-04 12:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02 20:38 [Qemu-devel] qemu dyngen.c exec-i386.c exec-i386.h exec.h op Fabrice Bellard
2003-06-04 10:38 ` Jerker Nyberg
2003-06-04 12:12   ` Falk Hueffner [this message]

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=87adcym48d.fsf@student.uni-tuebingen.de \
    --to=falk.hueffner@student.uni-tuebingen.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).