qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Marc E. Fiuczynski" <mef@CS.Princeton.EDU>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] PATCH for QEMU 0.6.1 hw/openpic.c typo bug
Date: Mon, 15 Nov 2004 14:31:44 -0500	[thread overview]
Message-ID: <NIBBJLJFDHPDIBEEKKLPEEMGCLAA.mef@cs.princeton.edu> (raw)
In-Reply-To: <4197CA1C.1010903@bellard.org>

Hello,

The hw/openpic.c code may have a typo error where a constant appears to have
an extra zero in it. I.e., it is
0x800000000 but should be
0x80000000.

This is something that gcc flags as a warning.  Considering the number of
other warning messages that gcc produces, I suspect that you guys have
simply overlooked this one. Below is a diff snippet that you can feed to
patch, though, I suppose it will be easier to edit it by hand.

Cheers,
Marc



*** hw/openpic.c        12 Nov 2004 19:42:16 -0000      1.1.1.1
--- hw/openpic.c        12 Nov 2004 21:05:24 -0000      1.2
***************
*** 629,635 ****
          break;
      case 0x10: /* TIBC */
        if ((opp->timers[idx].ticc & 0x80000000) != 0 &&
!           (val & 0x800000000) == 0 &&
              (opp->timers[idx].tibc & 0x80000000) != 0)
            opp->timers[idx].ticc &= ~0x80000000;
        opp->timers[idx].tibc = val;
--- 629,635 ----
          break;
      case 0x10: /* TIBC */
        if ((opp->timers[idx].ticc & 0x80000000) != 0 &&
!           (val & 0x80000000) == 0 &&
              (opp->timers[idx].tibc & 0x80000000) != 0)
            opp->timers[idx].ticc &= ~0x80000000;
        opp->timers[idx].tibc = val;

      reply	other threads:[~2004-11-15 19:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-14 21:11 [Qemu-devel] QEMU 0.6.1 is out Fabrice Bellard
2004-11-15 19:31 ` Marc E. Fiuczynski [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=NIBBJLJFDHPDIBEEKKLPEEMGCLAA.mef@cs.princeton.edu \
    --to=mef@cs.princeton.edu \
    --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).