Project

General

Profile

Task #7012

Implement means of managing the use of registers in a test program

Added by Andrei Tatarnikov over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
High
Category:
-
Target version:
Start date:
03/31/2016
Due date:
% Done:

100%

Estimated time:
Detected in build:
svn
Published in build:
2.3.31

Description

Need facilities to choose registers that are not in use and to make them free.

"Task 4 – get_register/free_register that talks to the model. Used by the branch engine as well to get/free registers that it requires. Must support parameters such as exclusion, and cpuID (or a function to reset which registers are reserved)"

History

#1

Updated by Andrei Tatarnikov over 3 years ago

  • Status changed from New to Open
  • % Done changed from 0 to 50

get_register/free_register were implemented. But they, currently, do not support the following stuff:

Must support parameters such as exclusion, and cpuID (or a function to reset which registers are reserved)"

#2

Updated by Andrei Tatarnikov over 3 years ago

Follow-up tasks:

  1. Implement exclusions. The get_register function should support selecting registers excluding some listed items. For example, it can look like this:
    get_register(:exclude => [x1, x2, x29])
  2. Implement the free_all_registers function. This is needed to describe test cases for multcore processors.
#3

Updated by Andrei Tatarnikov over 3 years ago

  • % Done changed from 50 to 60
free_all_registers is implemented: r6451, r6452, r6453
#4

Updated by Andrei Tatarnikov over 3 years ago

get_register(:exclude => [x1, x2, x29]) in progress:

r6454, r6455, r6456, r6457

Done

#5

Updated by Andrei Tatarnikov over 3 years ago

  • % Done changed from 60 to 100
#6

Updated by Andrei Tatarnikov over 3 years ago

  • Status changed from Open to Resolved
#7

Updated by Andrei Tatarnikov over 3 years ago

  • Status changed from Resolved to Closed
  • Published in build set to 2.3.31

Also available in: Atom PDF