From: Thiemo Seufer <ths@networkno.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to split vl.h
Date: Sun, 4 Nov 2007 18:06:35 +0000 [thread overview]
Message-ID: <20071104180635.GB9363@networkno.de> (raw)
In-Reply-To: <f43fc5580711040148m4175b7e1l13541c60af5c16d2@mail.gmail.com>
Blue Swirl wrote:
> On 11/1/07, Fabrice Bellard <fabrice@bellard.org> wrote:
> > Blue Swirl wrote:
> > > Hi,
> > >
> > > With the automatic dependency rule installed, modifying vl.h causes
> > > all files to be recompiled. This is of course the correct action, but
> > > it's a major slowdown for development too.
> >
> > There must be an option in the Makefile to disable the automatic
> > dependency check.
> >
> > > How should we split vl.h into smaller pieces? Give each device a
> > > header file, like m48t59? What about other stuff exported from vl.c?
> >
> > The net result is that you will have dozens of header files with only
> > one line in them as most devices only export one function.
>
> I have another solution: include all architecture specific files from
> the main file. This actually makes the compilation faster and the
> resulting binary is smaller (maybe faster).
I it a solution? You always end up with the worst case of recompiling
everything now.
> Changing the architecture
> specific code needs no changes to vl.h, just a recompile of sun4m.c,
> but this is instantaneous on my machine. Automatic dependencies also
> handle this case. I guess some may find this style pretty ugly.
It is ugly. You basically re-invented gcc's -combine option but
without avoiding the namespace problem of a single file scope.
Thiemo
prev parent reply other threads:[~2007-11-04 18:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 18:12 [Qemu-devel] How to split vl.h Blue Swirl
2007-10-31 19:35 ` Jocelyn Mayer
2007-10-31 23:06 ` Thiemo Seufer
2007-11-01 11:16 ` Fabrice Bellard
2007-11-01 13:32 ` Stefan Weil
2007-11-01 14:11 ` andrzej zaborowski
2007-11-04 8:48 ` Blue Swirl
2007-11-04 12:17 ` Paul Brook
2007-11-04 17:23 ` J. Mayer
2007-11-04 17:54 ` Paul Brook
2007-11-04 19:41 ` J. Mayer
2007-11-04 21:30 ` Paul Brook
2007-11-04 23:38 ` Thiemo Seufer
2007-11-04 18:06 ` Thiemo Seufer [this message]
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=20071104180635.GB9363@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 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.