Since this commit:
commit 999b53ec8794f203964db3ecf939a3da5c4bc843
Author: Claudio Fontana claudio.font...@linaro.org
Date: Wed Feb 5 17:27:28 2014 +
disas: Implement disassembly output for A64
Use libvixl to implement disassembly output in debug
logs for A64, for use with
On 15 February 2014 17:34, Michael Tokarev m...@tls.msk.ru wrote:
Since this commit:
commit 999b53ec8794f203964db3ecf939a3da5c4bc843
Author: Claudio Fontana claudio.font...@linaro.org
Date: Wed Feb 5 17:27:28 2014 +
disas: Implement disassembly output for A64
Use libvixl to
On 15 February 2014 18:12, Peter Maydell peter.mayd...@linaro.org wrote:
Ugh, sorry about that. I thought I'd caught them but obviously the Windows
32 bit build is pickier than the Linux one (it's clearly right though).
Incidentally if you have a simple recipe for setting up a windows
mingw
15.02.2014 22:53, Peter Maydell wrote:
Incidentally if you have a simple recipe for setting up a windows
mingw build environment on Ubuntu (preferably not bleeding-edge
Ubuntu) then I'm happy to add compile-test for win32 to my
pullreq application checklist.
Hm. I've never did that before,
On 15 February 2014 19:01, Michael Tokarev m...@tls.msk.ru wrote:
15.02.2014 22:53, Peter Maydell wrote:
Incidentally if you have a simple recipe for setting up a windows
mingw build environment on Ubuntu (preferably not bleeding-edge
Ubuntu) then I'm happy to add compile-test for win32 to my
15.02.2014 23:05, Peter Maydell wrote:
On 15 February 2014 19:01, Michael Tokarev m...@tls.msk.ru wrote:
BTW, current debian wheezy catches these constants
in 32bits too. I mean, when the host is 32bits.
Must be a new-gcc thing, then, maybe? My test 32 bit
Linux host has
On 15 February 2014 19:05, Peter Maydell peter.mayd...@linaro.org wrote:
On 15 February 2014 19:01, Michael Tokarev m...@tls.msk.ru wrote:
15.02.2014 22:53, Peter Maydell wrote:
Incidentally if you have a simple recipe for setting up a windows
mingw build environment on Ubuntu (preferably not
