From: Thiemo Seufer <ths@networkno.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH, RFC] Update disassembler files from latest binutils
Date: Sat, 25 Oct 2008 01:50:05 +0200 [thread overview]
Message-ID: <20081024235005.GD28588@networkno.de> (raw)
In-Reply-To: <f43fc5580810241212j35b8f450waa0db8eff8f96df5@mail.gmail.com>
Blue Swirl wrote:
> Hi,
>
> The disassembler files should be updated to get newer instructions
> supported. This is currently not easy because the *-dis.c files are
> concatenated using several files from binutils. There are some Qemu
> specific changes.
>
> The first patch introduces a new directory "dis", moves sparc-dis.c
> there, and splits it to three files as used in binutils: sparc-dis.c,
> sparc-opc.c and sparc.h.
>
> 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.
>
> I can introduce more staging patches if necessary. Comments?
Some files in Qemu are licensed as GPLv2 only. This is incompatible
with recent binutils files which are GPLv3 or later.
Thiemo
next prev parent reply other threads:[~2008-10-24 23:50 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 [this message]
2008-10-25 0:06 ` Paul Brook
2008-10-25 7:56 ` Blue Swirl
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=20081024235005.GD28588@networkno.de \
--to=ths@networkno.de \
--cc=blauwirbel@gmail.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).