qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/4] disas: add libvixl to support A64 disassemb


From: Alex Bennée
Subject: Re: [Qemu-devel] [PATCH 0/4] disas: add libvixl to support A64 disassembly
Date: Wed, 08 Jan 2014 14:51:19 +0000
User-agent: mu4e 0.9.9.6pre2; emacs 24.3.50.3

address@hidden writes:

> 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.

Is there an argument for making this an optional component. It would be
useful to know how many users care about having access to the target
assembly. Certainly I'm only looking at it while developing TCG code. 


Cheers,

--
Alex Bennée
QEMU/KVM Hacker for Linaro




reply via email to

[Prev in Thread] Current Thread [Next in Thread]