qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [5998] Fix TARGET_LONG_BITS warning in TCG
Date: Sat, 13 Dec 2008 13:48:20 +0200	[thread overview]
Message-ID: <f43fc5580812130348g694be982n786dcadef07b3771@mail.gmail.com> (raw)
In-Reply-To: <49439EF3.2010009@web.de>

On 12/13/08, Jan Kiszka <jan.kiszka@web.de> wrote:
> Blue Swirl wrote:
>  > On 12/13/08, Jan Kiszka <jan.kiszka@web.de> wrote:
>  >> Blue Swirl wrote:
>  >>  > On 12/13/08, Jan Kiszka <jan.kiszka@web.de> wrote:
>  >>  >> Blue Swirl wrote:
>  >>  >>  > Revision: 5998
>  >>  >>  >           http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5998
>  >>  >>  > Author:   blueswir1
>  >>  >>  > Date:     2008-12-13 08:16:43 +0000 (Sat, 13 Dec 2008)
>  >>  >>  >
>  >>  >>  > Log Message:
>  >>  >>  > -----------
>  >>  >>  > Fix TARGET_LONG_BITS warning in TCG
>  >>  >>  >
>  >>  >>  > Looking at tcg/tcg.c:828, the bug that the warning indicated would show up as
>  >>  >>  > incorrect PC shown in log, only on 32 bit big endian host emulating a 64 bit
>  >>  >>  > target, -d op flag enabled. Now that dyngen is gone, the patch can be applied.
>  >>  >>  >
>  >>  >>  > Modified Paths:
>  >>  >>  > --------------
>  >>  >>  >     trunk/tcg/tcg-runtime.c
>  >>  >>  >
>  >>  >>  > Modified: trunk/tcg/tcg-runtime.c
>  >>  >>  > ===================================================================
>  >>  >>  > --- trunk/tcg/tcg-runtime.c   2008-12-12 20:02:52 UTC (rev 5997)
>  >>  >>  > +++ trunk/tcg/tcg-runtime.c   2008-12-13 08:16:43 UTC (rev 5998)
>  >>  >>  > @@ -29,6 +29,7 @@
>  >>  >>  >
>  >>  >>  >  #include "config.h"
>  >>  >>  >  #include "osdep.h"
>  >>  >>  > +#include "cpu.h" // For TARGET_LONG_BITS
>  >>  >>  >  #include "tcg.h"
>  >>  >>  >
>  >>  >>  >  int64_t tcg_helper_shl_i64(int64_t arg1, int64_t arg2)
>  >>  >>  >
>  >>  >>
>  >>  >>
>  >>  >> Nice that this warning is finally fixed - but what is the point of
>  >>  >>  including all those headers at all here? [1] worked well for me while
>  >>  >>  reducing dependencies.
>  >>  >
>  >>  > I think all header files should be checked and even reorganized when
>  >>  > necessary. One item is the dyngen removal, cpu.h/exec.h distinction is
>  >>  > not clear for all targets and headers used by both user and system
>  >>  > emulators could be adjusted. Header files in hw should be OK, but
>  >>  > worth checking.
>  >>
>  >>
>  >> Header dependencies and usage policies should be rechecked and probably
>  >>  cleaned up now, no question (see also my dyngen-exec.h problems).
>  >>
>  >>  But here I was referring to the need of this _particular_ C file for any
>  >>  header except inttypes.h. Why including headers _here_ for no use?
>  >
>  > I tested the apparently harmless patch, but it isn't OK. osdep.h,
>  > qemu-log.h and tcg.h use FILE and size_t, and therefore we need at
>  > least stdio.h. Those headers should be fixed, then the patch would
>  > work.
>  >
>
>
> Sorry, confused: Which patch for which file do you mean now? If you
>  refer to mine: Why do we need osdep.h, qemu-log.h or tcg.h for
>  tcg-runtime.c?

This one:
http://permalink.gmane.org/gmane.comp.emulators.qemu/32076

They are not needed, but pulled in as a side product.

  reply	other threads:[~2008-12-13 11:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13  8:16 [Qemu-devel] [5998] Fix TARGET_LONG_BITS warning in TCG Blue Swirl
2008-12-13  9:23 ` [Qemu-devel] " Jan Kiszka
2008-12-13  9:43   ` Blue Swirl
2008-12-13  9:56     ` Jan Kiszka
2008-12-13 10:21       ` Blue Swirl
2008-12-13 11:11       ` Blue Swirl
2008-12-13 11:39         ` Jan Kiszka
2008-12-13 11:48           ` Blue Swirl [this message]
2008-12-13 12:46             ` Jan Kiszka

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=f43fc5580812130348g694be982n786dcadef07b3771@mail.gmail.com \
    --to=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 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).