From: Rob Landley <rob@landley.net>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu vs gcc4
Date: Mon, 30 Oct 2006 11:31:04 -0500 [thread overview]
Message-ID: <200610301131.05721.rob@landley.net> (raw)
In-Reply-To: <200610301456.07847.paul@codesourcery.com>
On Monday 30 October 2006 9:56 am, Paul Brook wrote:
> On Monday 30 October 2006 04:35, Rob Landley wrote:
> > On Monday 23 October 2006 1:58 pm, Paul Brook wrote:
> > > > Although, all told, it would seem to me that what might be called for
> > > > here is a new gcc target. A gcc target specifically for generating
> > > > qemu code. That would just simply generate whatever qemu wanted for
> > > > function postamble.
> > >
> > > Better to just teach qemu how to generate code.
> > > In fact I've already done most of the infrastructure (and a fair amount
> > > of the legwork) for this. The only major missing function is code to do
> > > softmmu load/store ops.
> > > https://nowt.dyndns.org/
> >
> > So given that one of the reasons for doing this would be getting away from
> > depending on specific and increasily out of date versions of gcc to build
> > the thing, what would be involved in getting this version to build under
> > gcc-4.x?
>
> Should work pretty much out the box. Obviously if you build anything other
> than m68k then all bets are off.
It didn't get to "work", it broke building. (The frighting part is that my
patch at http://busybox.net/downloads/qemu applied to your version without
rejects, but although that helped it get farther, it didn't finish.)
I just did a standard "./configure --shutupaboutthecompilerversion; make; make
install". (x86 is the first target I'm interested in, as it's the easiest to
test and you said it's using at least some of the new code...)
> Paul
Rob
--
"Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away." - Antoine de Saint-Exupery
next prev parent reply other threads:[~2006-10-30 16:31 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 18:53 [Qemu-devel] qemu vs gcc4 K. Richard Pixley
2006-10-22 22:06 ` Johannes Schindelin
2006-10-23 8:16 ` Martin Guy
2006-10-23 12:20 ` Paul Brook
2006-10-23 13:59 ` Avi Kivity
2006-10-23 14:10 ` Paul Brook
2006-10-23 14:28 ` Avi Kivity
2006-10-23 14:31 ` Paul Brook
2006-10-23 14:35 ` Avi Kivity
2006-10-23 17:41 ` K. Richard Pixley
2006-10-23 17:58 ` Paul Brook
2006-10-23 18:04 ` K. Richard Pixley
2006-10-23 18:20 ` Laurent Desnogues
2006-10-23 18:37 ` Paul Brook
2006-10-24 23:39 ` Rob Landley
2006-10-25 0:24 ` Paul Brook
2006-10-25 19:39 ` Rob Landley
2006-10-26 18:09 ` Daniel Jacobowitz
2006-10-31 16:53 ` Rob Landley
2006-10-31 19:02 ` Paul Brook
2006-10-31 20:41 ` Rob Landley
2006-10-31 22:08 ` Paul Brook
2006-10-31 22:31 ` Laurent Desnogues
2006-10-31 23:00 ` Paul Brook
2006-11-01 0:00 ` Rob Landley
2006-11-01 0:29 ` Paul Brook
2006-11-01 1:51 ` Rob Landley
2006-11-01 3:22 ` Paul Brook
2006-11-01 16:34 ` Rob Landley
2006-11-01 17:01 ` Paul Brook
2006-10-31 23:17 ` Rob Landley
2006-11-01 0:01 ` Paul Brook
2006-10-30 4:35 ` Rob Landley
2006-10-30 14:56 ` Paul Brook
2006-10-30 16:31 ` Rob Landley [this message]
2006-10-30 16:50 ` Paul Brook
2006-10-30 22:54 ` Stephen Torri
2006-10-30 23:13 ` Paul Brook
2006-10-23 1:27 ` Rob Landley
2006-10-23 1:44 ` Paul Brook
2006-10-23 1:45 ` Johannes Schindelin
2006-10-23 17:53 ` K. Richard Pixley
2006-10-23 18:08 ` Rob Landley
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=200610301131.05721.rob@landley.net \
--to=rob@landley.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.