From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] use stdio.h
Date: Mon, 24 Apr 2006 16:08:58 +0100 [thread overview]
Message-ID: <200604241608.59335.paul@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0604241702090.26453@mag.sysgo.com>
> >> Make dyngen-exec.h include <stdio.h> which is more portable than the
> >> local definitions.
> >
> > I believe dyngen-exec.h deliberately doesn't include stdio.h because it
> > conflicts with the local register variables on some hosts.
>
> Ah, I thought there's got to be an explanation... Should be added though to
> dyngen-exec.h to avoid future patches from wise-guys like myself :-)
From the top of that file:
/* NOTE: standard headers should be used with special care at this
point because host CPU registers are used as global variables. Some
host headers do not allow that. */
Paul
prev parent reply other threads:[~2006-04-24 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 14:40 [Qemu-devel] [PATCH] use stdio.h Marius Groeger
2006-04-24 14:46 ` Paul Brook
2006-04-24 15:04 ` Marius Groeger
2006-04-24 15:08 ` Paul Brook [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=200604241608.59335.paul@codesourcery.com \
--to=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).