From: "Jim C. Brown" <jbrown106@phreaker.net>
To: jhoger@pobox.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] get_func() hangs with gcc 3.4.2 on MinGW and WinXP host
Date: Sat, 18 Dec 2004 16:59:47 -0500 [thread overview]
Message-ID: <20041218215947.GA7207@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <1103404056.21895.83.camel@aragorn>
On Sat, Dec 18, 2004 at 01:07:36PM -0800, John R. Hogerhuis wrote:
> On Sat, 2004-12-18 at 06:59, Johannes Schindelin wrote:
>
> The path of least resistance to get there would be to generate op.s
> files (using the necessary version of GCC) for all popular CPUs, and
> make them part of the build. Then those could be hand optimized over
> time as folks have the spare cycles to do it. This would remove specific
> gcc version dependencies from the build with little effort.
>
That works quite well for now. Of course, if qemu is suddenly ported to a new
CPU arch, then it is likely that the new op.s file needed would have to be
hand coded. Still, a reasonable compromise.
> Unless that's a GPL violation (distributing generated code under a
> non-GPL license)... don't know about that angle.
It is not. GPL only applies to derived code. Generated code is derivied from
what you right, not from the gcc source code, and thus the GPL doesn't apply
to it. So the op.s files would share the same copyright as the original op.c
file.
> If that were the case,
> the only option along this line would be coding from scratch unless GPL
> is acceptable for the core. [QEMU uses mixed licensing and I don't have
> it straight in my head, sorry.]
QEMU uses BSD/MIT license for the system emulator.
It is qemu-user (the linux only one) which is GPL.
>
> -- John.
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2004-12-18 22:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 13:47 [Qemu-devel] get_func() hangs with gcc 3.4.2 on MinGW and WinXP host tomba
2004-12-15 14:18 ` Johannes Schindelin
2004-12-15 14:59 ` tomba
2004-12-15 23:45 ` Jim C. Brown
2004-12-15 23:52 ` Johannes Schindelin
2004-12-17 18:56 ` Juergen Lock
2004-12-18 0:09 ` Johannes Schindelin
2004-12-18 4:04 ` Jim C. Brown
2004-12-18 14:59 ` Johannes Schindelin
2004-12-18 15:50 ` Jim C. Brown
2004-12-19 14:25 ` Johannes Schindelin
2004-12-19 22:57 ` Jim C. Brown
2004-12-18 21:07 ` John R. Hogerhuis
2004-12-18 21:59 ` Jim C. Brown [this message]
2004-12-19 14:45 ` Johannes Schindelin
2004-12-20 6:26 ` John R. Hogerhuis
2004-12-20 15:16 ` Removing GCC dependency, was " Johannes Schindelin
2004-12-20 18:02 ` John R. Hogerhuis
2004-12-20 23:30 ` Fabrice Bellard
2004-12-21 14:36 ` [Qemu-devel] Testing with Win2k SP3 and Win2kSP4 Elefterios Stamatogiannakis
2004-12-21 15:23 ` [Qemu-devel] Re: Removing GCC dependency Paul Brook
2004-12-21 15:36 ` Herbert Poetzl
2004-12-19 22:13 ` [Qemu-devel] get_func() hangs with gcc 3.4.2 on MinGW and WinXP host Fabrice Bellard
2004-12-19 22:29 ` Johannes Schindelin
2004-12-20 3:31 ` Rob Browning
2004-12-20 18:57 ` John R. Hogerhuis
2005-01-17 14:16 ` CMinusMins, was " Johannes Schindelin
2005-01-17 15:36 ` malc
2005-01-17 15:53 ` Jim C. Brown
2005-01-17 16:13 ` OCAML, was " Mark A. Williamson
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=20041218215947.GA7207@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--cc=jhoger@pobox.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).