Mailing List Archives

Authenticated access

 		[Computer Systems Lab]

[← Prev]  [Date]  [Next →] [← Prev]  [Thread]  [Next →]

[Gems-users] Assertion Failed in GEMS1.4

Date: Sat, 19 May 2007 15:06:12 -0700 (PDT)
From: James Wang <jameswang99@xxxxxxxxx>
Subject: [Gems-users] Assertion Failed in GEMS1.4 
Hi All:
    I have made a customized transactional memory protocol. The same deque benchmark works fine on GEMS1.3 but  fails an assertion in GEMS1.4. The assertion seems to be in TransactionManager::delayRestart()         ASSERT(p != getID()); // DEADLOCK! 
    Any idea what it means? Thanks in advance for any reply.
 
Regards
James
[← Prev in Thread] Current Thread [Next in Thread→]
  • [Gems-users] Assertion Failed in GEMS1.4, James Wang <=
Previous by Date:  Re: [Gems-users] Opal "Caught time breakpoint", Lei Yang
Next by Date:  [Gems-users] TLB misses, Ruby and Simics, mehmetderin . harmanci
Previous by Thread:  Re: [Gems-users] Another question about gems1.4 with x86 target, Dan Gibson
Next by Thread:  [Gems-users] Barrier using Ruby., Sreenivasan Padmanabhan
Indexes:  [Date] [Thread]