From: "Blue Swirl" <blauwirbel@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] Update disassembler files from latest binutils
Date: Sat, 25 Oct 2008 10:56:39 +0300 [thread overview]
Message-ID: <f43fc5580810250056g2942594ke98c62958ecc5ad1@mail.gmail.com> (raw)
In-Reply-To: <200810250106.50402.paul@codesourcery.com>
On 10/25/08, Paul Brook <paul@codesourcery.com> wrote:
> > The second patch updates the files from binutils 2.18. The real
> > changes from 2002 binutils to current are not that large, but there is
> > some code movement and I changed tabs to spaces at one point. The
> > license changes from GPL v2 to v3.
>
>
> GPLv3 is not acceptable for qemu, which contains v2 only code.
We could update once to binutils 2.17 which is GPL v2+. For Sparc this
would be about OK, since there is just one commit after GPLv3 switch.
But for i386 this would mean missing 30 to 50 commits.
Alternatively we could develop new disassemblers, for example based on
translate.c code (LGPL v2 for Sparc). Easy for Sparc, but a huge job
for i386/amd64.
next prev parent reply other threads:[~2008-10-25 7:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f43fc5580810241101ra7099ddj260f6eb36a2edd35@mail.gmail.com>
2008-10-24 19:12 ` [Qemu-devel] [PATCH, RFC] Update disassembler files from latest binutils Blue Swirl
2008-10-24 19:36 ` Kirill A. Shutemov
2008-10-24 19:46 ` Blue Swirl
2008-10-24 19:38 ` Andreas Färber
2008-10-24 19:59 ` Blue Swirl
2008-10-24 20:05 ` Aurelien Jarno
2008-10-24 20:16 ` Stefan Weil
2008-10-24 23:48 ` Thiemo Seufer
2008-10-24 23:50 ` Thiemo Seufer
2008-10-25 0:06 ` Paul Brook
2008-10-25 7:56 ` Blue Swirl [this message]
2008-10-25 10:17 ` Laurent Desnogues
2008-10-27 8:54 ` Laurent Desnogues
2008-10-27 9:37 ` Laurent Desnogues
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=f43fc5580810250056g2942594ke98c62958ecc5ad1@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).