summaryrefslogtreecommitdiff
path: root/regress/include/bitstring/good/67
diff options
context:
space:
mode:
authorwiz <wiz@NetBSD.org>2004-01-12 21:17:30 +0000
committerwiz <wiz@NetBSD.org>2004-01-12 21:17:30 +0000
commite72df29d6dcf8174772da170deea6ff15aa3d915 (patch)
tree9c45e8d7b445b519a4aec6ec396ef42c52083352 /regress/include/bitstring/good/67
parent73abe3ee522453c23adb5ddf0d81303ce9084016 (diff)
Bump date for previous. Punctuation nits. Sort SEE ALSO.
Diffstat (limited to 'regress/include/bitstring/good/67')
0 files changed, 0 insertions, 0 deletions
such a drastic state change happens, but might as well have this correct. The changes made are: 1) Since having rf_State_DecrAccessCount() come after rf_State_Cleanup() is just fine, change rf_layout.c to reflect that rf_DecrAccessesCountState comes after rf_Cleanup_State (i.e. they swap positions in the state list). This means that going to rf_Cleanup_State after bailing on a failed DAG access will do all the right things -- the state will get cleaned up, and then the access counts will get decremented properly. The comment in rf_State_ProcessDAG() is now actually correct -- the next state *will* be rf_Cleanup_State. 2) Move rf_DecrAccessesCountState in RF_AccessState_e to just after rf_CleanupState. This puts RF_AccessState_e in sync with DefaultStates[]. Fortunately, these states are rarely referred to by name, and so this change ends up being mostly cosmetic -- it really only fixes cleanup behaviour for the recent "Failed to create a DAG" changes. 2003-12-30Some days you wonder if some of the function declaration consistencyoster was just an accident in the first place. Cleanup function decls and a few comments. [ok.. so I wasn't going to fix this many.. but once you're on a roll....] 2003-02-09constify somejdolecek 2002-09-23dataBytesPerStripe is set, but never used. *poof*oster