From: qemu-devel@email.fries.net
To: "????????? (Wei-Ren Chen)" <chenwj@iis.sinica.edu.tw>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] large memory requirements for translate.c a barrier
Date: Fri, 22 Mar 2013 10:19:18 -0500 [thread overview]
Message-ID: <20130322151918.GA6921@fries.net> (raw)
In-Reply-To: <20130322073014.GA66600@cs.nctu.edu.tw>
Penned by ????????? (Wei-Ren Chen) on 20130322 2:30.14, we have:
| > Still no joy:
| >
| > PID USERNAME PRI NICE SIZE RES STATE WAIT TIME CPU COMMAND
| > 21212 todd -5 20 1142M 118M sleep/0 - 1:03 37.30% cc1
| >
| > cc -I. -I/home/todd/git/sw/3rdParty/qemu -I/home/todd/git/sw/3rdParty/qemu/include -I/home/todd/git/sw/3rdParty/qemu/tcg -I/home/todd/git/sw/3rdParty/qemu/tcg/i386 -fPIE -DPIE -m32 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -I/usr/local/include -I/usr/X11R6/include -Wno-redundant-decls -DTIME_MAX=INT_MAX -fno-gcse -fno-var-tracking -fstack-protector-all -Wendif-labels -Wmissing-include-dirs -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wold-style-definition -I/usr/local/include/libpng -I/usr/X11R6/include/pixman-1 -DHAS_AUDIO -DHAS_AUDIO_CHOICE -I/home/todd/git/sw/3rdParty/qemu/target-i386 -Itarget-i386 -I.. -I/home/todd/git/sw/3rdParty/qemu/target-i386 -DNEED_CPU_H -I/home/todd/git/sw/3rdParty/qemu/include -pthread -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -MMD -MP -MT target-i386/kvm-stub.o -MF target-i386/kvm-stub.d -O2 -D_FORTIFY_SOURCE=2 -g -c -o target-i386/kvm-stub.o /home/todd/git/sw/3rdParty/qemu/target-i386/kvm-stub.c
|
| Is it possible to update your GCC, or try to use clang?
OpenBSD is using the latest gcc that is not GPLv3 for license reasons for the
base os.
In ports there are newer versions of gcc for programs that require it to build,
and clang is available also.
It doesn't make sense to switch compilers because this does build, so I will
either find time to take a stab at moving things out of translate.c or deal
with the excessive memory this file takes to build per softmmu target before
I try using a compiler that is not what any other OpenBSD user is going to
be running qemu with.
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)
| PO Box 16169, Oklahoma City, OK 73113 \ 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
next prev parent reply other threads:[~2013-03-22 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 19:21 [Qemu-devel] large memory requirements for translate.c a barrier Todd T. Fries
2013-03-16 8:14 ` Paolo Bonzini
2013-03-19 15:05 ` qemu-devel
2013-03-21 7:53 ` qemu-devel
2013-03-21 8:25 ` Paolo Bonzini
2013-03-22 7:08 ` qemu-devel
2013-03-22 7:30 ` 陳韋任 (Wei-Ren Chen)
2013-03-22 15:19 ` qemu-devel [this message]
2013-03-22 15:28 ` Peter Maydell
2013-03-22 9:34 ` Paolo Bonzini
2013-03-19 15:18 ` Andreas Färber
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=20130322151918.GA6921@fries.net \
--to=qemu-devel@email.fries.net \
--cc=chenwj@iis.sinica.edu.tw \
--cc=pbonzini@redhat.com \
--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 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).