1. Aug 09, 2017
    • Andrew Waterman's avatar
      Don't merge stores that manifest WAW hazards · d54dca43
      Andrew Waterman authored
      The following sequence would drop the first store when eccBytes=4:
      
          sb x0, 0(t0)
          nop
          sb x0, 4(t0)
          nop
          sb x0, 1(t0)
      
      Because the first and second store are to different ECC granules, the
      hazard check correctly allowed the second one to proceed, but the third
      was merged with the second, even though it conflicted with the first.
      So, don't allow the third to be merged with the second, since the second
      stored to a different ECC granule.
      d54dca43
  2. Aug 08, 2017
  3. Aug 07, 2017
  4. Aug 06, 2017
  5. Aug 05, 2017
  6. Aug 04, 2017
  7. Aug 03, 2017