From: Stefan Weil <sw@weilnetz.de>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: patches@linaro.org, "Alexander Graf" <agraf@suse.de>,
"Blue Swirl" <blauwirbel@gmail.com>,
"Claudio Fontana" <claudio.fontana@linaro.org>,
"Christoffer Dall" <christoffer.dall@linaro.org>,
"Anthony Liguori" <aliguori@amazon.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
kvmarm@lists.cs.columbia.edu,
"Aurélien Jarno" <aurelien@aurel32.net>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 0/4] disas: add libvixl to support A64 disassembly
Date: Tue, 07 Jan 2014 23:53:48 +0100 [thread overview]
Message-ID: <52CC857C.7000901@weilnetz.de> (raw)
In-Reply-To: <1389113488-18005-1-git-send-email-peter.maydell@linaro.org>
Am 07.01.2014 17:51, schrieb Peter Maydell:
> Hi. This is a rebased and mildly cleaned up version of Claudio's
> RFC patchset from last year to add libvixl to QEMU and use it
> for A64 disassembly.
>
> NOTE NOTE NOTE
> * we now link with g++, not gcc (even if the target doesn't
> happen to need the A64 disassembler, since it's a bit hard
> to tell whether there's a C++-source .o file in the link)
> * I've tested Linux (including static link of linux-user) and
> MacOS hosts, but not Windows
> * if you have a visceral dislike of the idea of C++ in the
> QEMU binary now would be a good time to say OMG WTF BBQ
For w32, C++ (currently only aarch64 executables) means loading
additional DLL files:
text data bss dec hex filename
91453 1636 1012 94101 16f95
/usr/lib/gcc/i686-w64-mingw32/4.6/libgcc_s_sjlj-1.dll
796376 29784 3744 829904 ca9d0
/usr/lib/gcc/i686-w64-mingw32/4.6/libstdc++-6.dll
They slightly increase the load time and the memory footprint (reducing
the meory which is available for QEMU system emulation), but I think
this can be neglected. The Windows installers will get larger of course,
too.
For Linux, QEMU will have new dependencies (libstdc++, maybe more) for
the aarch64 executables. CC'ing Aurelien therefore.
Regards
Stefan
next prev parent reply other threads:[~2014-01-07 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 16:51 [Qemu-devel] [PATCH 0/4] disas: add libvixl to support A64 disassembly Peter Maydell
2014-01-07 16:51 ` [Qemu-devel] [PATCH 1/4] rules.mak: Support .cc as a C++ source file suffix Peter Maydell
2014-01-07 16:51 ` [Qemu-devel] [PATCH 2/4] rules.mak: Link with C++ if we have a C++ compiler Peter Maydell
2014-01-07 16:51 ` [Qemu-devel] [PATCH 3/4] disas: add libvixl source code for AArch64 A64 disassembler Peter Maydell
2014-01-07 16:51 ` [Qemu-devel] [PATCH 4/4] disas: Implement disassembly output for A64 Peter Maydell
2014-01-07 22:30 ` [Qemu-devel] [PATCH 0/4] disas: add libvixl to support A64 disassembly Stefan Weil
2014-01-07 23:00 ` Peter Maydell
2014-01-08 6:55 ` Stefan Weil
2014-01-08 10:07 ` Peter Maydell
2014-01-07 22:53 ` Stefan Weil [this message]
2014-01-08 14:51 ` Alex Bennée
2014-01-08 15:31 ` Peter Maydell
2014-01-08 16:19 ` Alexander Graf
2014-01-07 23:46 ` Peter Maydell
2014-01-08 14:48 ` Alex Bennée
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=52CC857C.7000901@weilnetz.de \
--to=sw@weilnetz.de \
--cc=agraf@suse.de \
--cc=alex.bennee@linaro.org \
--cc=aliguori@amazon.com \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=christoffer.dall@linaro.org \
--cc=claudio.fontana@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.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.