From: Ricky Z. <zha...@gm...> - 2016-08-19 16:55:17
|
Recently, I'm working on fixing several issues in BII Linux and Mac host. I found something I'd like to work on to make BII work in modern Mac/Linux OS: 1. Warnings from clang. Some are bugs like undefined behavior and sequence points in modern compilers. Some are 64bit compatible issues. Those are easy to fix. 2. Plan for slirp. a. Leave it as it is? Recommend to use tun/tap in Mac and Linux? I think tun/tap is more favorable than other. b. Migrate to a complete new slirp from QEMU. c. Just fix 64 bit issue in current code base. Personally I prefer choice a. Just because of less work. But there may be some configuration hassle in Mac to setup tup/tap. 3. JIT. It doesn't quite work well with recent GCC, Clang and even 32bit ARM platform. I haven't read into details how it works. So I don't have any proposed plan yet. But I did see QEMU have been using new TCG to handle instruction emulation. Is JIT in BII a port from QEMU old dynamic translator technique? Any document except TECH manual to guide me? TIA |