Re: [Qemu-devel] [RFC] Disassembler options going forward

2013-02-14 Thread Anthony Liguori
Peter Maydell writes: > On 14 February 2013 21:10, Richard Henderson wrote: >> The only options I can see going forward are >> >> 1) Provide a configure time option to link to the "system" libopcodes. >> 2) Use someone else's (bsd licensed?) disassember. >> 3) Rearrange relevant translators s

Re: [Qemu-devel] [RFC] Disassembler options going forward

2013-02-14 Thread Blue Swirl
On Thu, Feb 14, 2013 at 9:10 PM, Richard Henderson wrote: > On 02/13/2013 06:28 PM, Anthony Liguori wrote: >> QEMU is GPLv2 only so we can't take GPLv3 code. We're stuck on binutils >> code that predates the v3 relicense. > > Ok, this is something that's going to bite us more and more. > > We nee

Re: [Qemu-devel] [RFC] Disassembler options going forward

2013-02-14 Thread Anthony Liguori
Richard Henderson writes: > On 02/13/2013 06:28 PM, Anthony Liguori wrote: >> QEMU is GPLv2 only so we can't take GPLv3 code. We're stuck on binutils >> code that predates the v3 relicense. > > Ok, this is something that's going to bite us more and more. > > We need *some* solution that allows u

Re: [Qemu-devel] [RFC] Disassembler options going forward

2013-02-14 Thread Peter Maydell
On 14 February 2013 21:10, Richard Henderson wrote: > The only options I can see going forward are > > 1) Provide a configure time option to link to the "system" libopcodes. > 2) Use someone else's (bsd licensed?) disassember. > 3) Rearrange relevant translators so that they can disassemble and

[Qemu-devel] [RFC] Disassembler options going forward

2013-02-14 Thread Richard Henderson
On 02/13/2013 06:28 PM, Anthony Liguori wrote: > QEMU is GPLv2 only so we can't take GPLv3 code. We're stuck on binutils > code that predates the v3 relicense. Ok, this is something that's going to bite us more and more. We need *some* solution that allows us to disassemble current cpus. What we