diff options
| author | Steve Reinhardt <stever@gmail.com> | 2008-06-13 01:29:20 -0400 |
|---|---|---|
| committer | Steve Reinhardt <stever@gmail.com> | 2008-06-13 01:29:20 -0400 |
| commit | 024ec4c5c310b1225a52532d41d5cc9f2633ae6c (patch) | |
| tree | e2792fceab44c2fe9518fd40d2d5ad27d74de945 /src/mem/tport.cc | |
| parent | 2b4874449ce45504a1759c593a1f9b00983fca01 (diff) | |
| download | gem5-024ec4c5c310b1225a52532d41d5cc9f2633ae6c.tar.xz | |
Get rid of bogus cache assertion.
I was asserting that the only reason you would defer targets is if
a write came in while you had an outstanding read miss, but there's
another case where you could get a read access after you've snooped
an invalidation and buffered it because it applies to a prior
outstanding miss.
Diffstat (limited to 'src/mem/tport.cc')
0 files changed, 0 insertions, 0 deletions