From: Blue Swirl <blauwirbel@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] Smarter compilation for target devices
Date: Tue, 28 Apr 2009 19:18:07 +0300 [thread overview]
Message-ID: <f43fc5580904280918v7bbfc480v9124a9896880a63d@mail.gmail.com> (raw)
In-Reply-To: <200904281432.42291.paul@codesourcery.com>
On 4/28/09, Paul Brook <paul@codesourcery.com> wrote:
> > Compile target devices only once for each endian and word size combination,
> > saving a few compiles if large number of targets are enabled.
>
>
> > +CPPFLAGS=-I. -I.. -I$(SRC_PATH) -MMD -MT $@ -MP -DNEED_CPU_H
>
>
> > +# Warning: Do not add new files here if they have conditional code
> > +# with #ifdef TARGET_xxx etc, use TARGET_PAGE_SIZE or reference
> > +# CPUState
>
>
> This is just asking for trouble. Anything that includes cpu.h must be rebuilt
> for every cpu. IMO a necessary prerequisite for this change is reworking
> header files so that you can't accidentally use the wrong symbols.
Yes, this was a hack. I think with your header change it will be much cleaner.
> Also, which bitwidth are you intending to distinguish here? target_ulong or
> target_phys_addr_t? With a few exceptions, devices don't care about the
target_phys_addr_t, of course. The devices that know about
target_ulong (or CPUState, TARGET_PAGE_SIZE) can't use this system.
> former. Duplicating this logic is both cpu.h and configure is also asking for
> trouble. At minimum the build should fail if they disagree.
Which logic?
next prev parent reply other threads:[~2009-04-28 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 19:34 [Qemu-devel] [PATCH, RFC] Smarter compilation for target devices Blue Swirl
2009-04-28 13:32 ` Paul Brook
2009-04-28 16:18 ` Blue Swirl [this message]
2009-04-28 17:25 ` Paul Brook
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=f43fc5580904280918v7bbfc480v9124a9896880a63d@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).