From: Michael Jennings <mej@eterm.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Seg Faults from 0.5.4
Date: Thu, 6 May 2004 11:04:55 -0400 [thread overview]
Message-ID: <20040506150455.GA24214@kainx.org> (raw)
In-Reply-To: <20040506134822.GB31514@MAIL.13thfloor.at>
On Thursday, 06 May 2004, at 15:48:22 (+0200),
Herbert Poetzl wrote:
> not convinced that this is the reason, but I'd try with a 3.3 or 3.4
> gcc as 3.2.x had some issues with the optimization ...
The optimization of the qemu code as it's compiled? I built using
"-O2 -march=pentium" if that makes a difference...should I try -O0 or
-O1 instead? Perhaps build for a different architecture?
Unfortunately I don't have gcc 3.4 packaged quite yet, but I should
within the next week or so.
Thanks!
Michael
--
Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <mej@kainx.org>
n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
"IMPORTANT NOTICE: If you are one of the hundreds of parachuting
enthusiasts who bought our 'Easy Sky Diving' book, please make the
following correction: on page 8, line 7, the words 'state zip
code' should have read 'pull rip cord.'"
-- notice appearing in a Warrenton, Virginia, newspaper
prev parent reply other threads:[~2004-05-06 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 18:35 [Qemu-devel] Seg Faults from 0.5.4 Michael Jennings
2004-05-04 20:20 ` Martin Garton
2004-05-04 20:40 ` Michael Jennings
2004-05-04 22:24 ` Martin Garton
2004-05-04 22:41 ` Herbert Poetzl
2004-05-05 2:13 ` Michael Jennings
2004-05-06 13:48 ` Herbert Poetzl
2004-05-06 15:04 ` Michael Jennings [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=20040506150455.GA24214@kainx.org \
--to=mej@eterm.org \
--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).