From: Christian Wiese <developlists@gmx.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] BeOS/Zeta eats 100% cpu time
Date: Fri, 01 Oct 2004 23:06:20 +0200 [thread overview]
Message-ID: <415DC6CC.9060600@gmx.de> (raw)
In-Reply-To: <415D11FA.4020004@gmx.de>
Christian Wiese wrote:
> Maybe I find some time to build an profiling-enabled version.
Hmm, when I set -p or -pg for profiling and remove
-fomit-frame-pointer, the created op.h is empty and dyngen crashes
because of this. Does someone now why this happen and what I can do to
get a profiling-executable?
Greetings,
Chris
next prev parent reply other threads:[~2004-10-01 21:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 13:32 [Qemu-devel] BeOS/Zeta eats 100% cpu time Christian Wiese
2004-09-30 15:36 ` André Braga
2004-09-30 15:53 ` Christian Wiese
2004-09-30 17:07 ` André Braga
2004-09-30 17:27 ` Christian Wiese
2004-09-30 18:38 ` André Braga
2004-09-30 21:22 ` Andreas Bollhalder
2004-10-01 8:14 ` Christian Wiese
2004-10-01 16:24 ` André Braga
2004-10-01 21:06 ` Christian Wiese [this message]
2004-10-01 22:24 ` Paul Brook
2004-10-02 3:45 ` Johannes Schindelin
2004-10-03 18:57 ` Christian Wiese
2004-10-04 6:41 ` Johannes Schindelin
2004-10-04 8:09 ` Christian Wiese
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=415DC6CC.9060600@gmx.de \
--to=developlists@gmx.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).