All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Todd T. Fries" <qemu-devel@email.fries.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] OpenBSD progress.. available for testing
Date: Wed, 16 Dec 2009 01:15:06 -0600	[thread overview]
Message-ID: <20091216071506.GC31470@fries.net> (raw)

For anyone lurking wanting a newer port of qemu to OpenBSD, I've determined
that -O0 is required for cpu-exec.o and suddely things start working!

Will try to determine why while updating other diffs to current qemu perhaps
in time for the 0.12.0 release, but at least finally I can run the 0.12.0rc1
on OpenBSD/i386 for the first time since the 0.9.1 release.

Thanks much to brynet at gmail dot com for pointing out the -O0 trick, though
I have narrowed it down to cpu-exec.o.

Are there any gcc4 assumptions in there incase my spend time investigating
can be shaved?

Thanks,
-- 
Todd Fries .. todd@fries.net

 _____________________________________________
|                                             \  1.636.410.0632 (voice)
| Free Daemon Consulting, LLC                 \  1.405.227.9094 (voice)
| http://FreeDaemonConsulting.com             \  1.866.792.3418 (FAX)
| 2525 NW Expy #525, Oklahoma City, OK 73112  \  sip:freedaemon@ekiga.net
| "..in support of free software solutions."  \  sip:4052279094@ekiga.net
 \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
                                                 
              37E7 D3EB 74D0 8D66 A68D  B866 0326 204E 3F42 004A
                        http://todd.fries.net/pgp.txt

             reply	other threads:[~2009-12-16  7:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16  7:15 Todd T. Fries [this message]
2009-12-16  7:49 ` [Qemu-devel] OpenBSD progress.. available for testing Todd T. Fries

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=20091216071506.GC31470@fries.net \
    --to=qemu-devel@email.fries.net \
    --cc=qemu-devel@nongnu.org \
    --cc=todd@fries.net \
    /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.