)]}'
{
  "commit": "328aaa626fbbc3d664086b6dd4bde11bd71f9d5d",
  "tree": "5a04b0e5ed8e94e3f93d776ea9e82e71d1a1680e",
  "parents": [
    "f4559a703f16d98c9142bba6c51bc9d85ad684ec"
  ],
  "author": {
    "name": "Roger Chang",
    "email": "rogerycchang@google.com",
    "time": "Tue Jun 13 17:25:47 2023 +0800"
  },
  "committer": {
    "name": "Bobby Bruce",
    "email": "bbruce@ucdavis.edu",
    "time": "Thu Jun 15 20:10:04 2023 +0000"
  },
  "message": "arch-riscv: Fix unexpected behavior of float operations in Mac OS\n\nThe uint_fast16_t is the integer at least 16 bits size, it can be\n32, 64 bits and more. Usually most of the simulations are in the\nx86-64 linux host, the size of uint_fast16_t is 64 bits. Therefore,\nthere is no problem for double precision float operations and it can\npass FloatMM test. However, in the Mac OS, the size of uint_fast16_t\nis 16 bits, it will lose the upper bits when converting float\nregister bits to freg_t and it will generate unexpected results for\nFloatMM test.\n\nThe change can guarantee that the size of data in freg_t is at least\n64 bits and it will not lose any data from floating point to freg_t.\n\nReference:\nhttps://developer.apple.com/documentation/kernel/uint_fast16_t\n\nhttps://codebrowser.dev/glibc/glibc/stdlib/stdint.h.html\n\nChange-Id: I3df6610f0903cdee0f56584d6cbdb51ac26c86c8\nReviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/71519\nMaintainer: Bobby Bruce \u003cbbruce@ucdavis.edu\u003e\nTested-by: kokoro \u003cnoreply+kokoro@google.com\u003e\nReviewed-by: Bobby Bruce \u003cbbruce@ucdavis.edu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1654bdb627156e974cb3598e43594f31073507fa",
      "old_mode": 33188,
      "old_path": "src/arch/riscv/regs/float.hh",
      "new_id": "4809372070ada19fea02cc054f3bf48c72f37f87",
      "new_mode": 33188,
      "new_path": "src/arch/riscv/regs/float.hh"
    }
  ]
}