Searched hist:9996 (Results 1 - 4 of 4) sorted by relevance

/gem5/src/mem/slicc/ast/
H A DInPortDeclAST.pydiff 9996:150338b8ba12 Fri Dec 20 21:34:00 EST 2013 Nilay Vaish <nilay@cs.wisc.edu> ruby: slicc: replace max_in_port_rank with number of inports

This patch replaces max_in_port_rank with the number of inports. The use of
max_in_port_rank was causing spurious re-builds and incorrect initialization
of variables in ruby related regression tests. This was due to the variable
value being used across threads while compiling when it was not meant to be.

Since the number of inports is state machine specific value, this problem
should get solved.
/gem5/src/mem/ruby/slicc_interface/
H A DAbstractController.ccdiff 9996:150338b8ba12 Fri Dec 20 21:34:00 EST 2013 Nilay Vaish <nilay@cs.wisc.edu> ruby: slicc: replace max_in_port_rank with number of inports

This patch replaces max_in_port_rank with the number of inports. The use of
max_in_port_rank was causing spurious re-builds and incorrect initialization
of variables in ruby related regression tests. This was due to the variable
value being used across threads while compiling when it was not meant to be.

Since the number of inports is state machine specific value, this problem
should get solved.
H A DAbstractController.hhdiff 9996:150338b8ba12 Fri Dec 20 21:34:00 EST 2013 Nilay Vaish <nilay@cs.wisc.edu> ruby: slicc: replace max_in_port_rank with number of inports

This patch replaces max_in_port_rank with the number of inports. The use of
max_in_port_rank was causing spurious re-builds and incorrect initialization
of variables in ruby related regression tests. This was due to the variable
value being used across threads while compiling when it was not meant to be.

Since the number of inports is state machine specific value, this problem
should get solved.
/gem5/src/mem/slicc/symbols/
H A DStateMachine.pydiff 9996:150338b8ba12 Fri Dec 20 21:34:00 EST 2013 Nilay Vaish <nilay@cs.wisc.edu> ruby: slicc: replace max_in_port_rank with number of inports

This patch replaces max_in_port_rank with the number of inports. The use of
max_in_port_rank was causing spurious re-builds and incorrect initialization
of variables in ruby related regression tests. This was due to the variable
value being used across threads while compiling when it was not meant to be.

Since the number of inports is state machine specific value, this problem
should get solved.

Completed in 33 milliseconds