I don't think so.
Research of this code is just starting.
Don't give up.
Update is not the most effecient, Guess is not the most effecint.
dukuso2 wrote:what's the most inner critical loop ?
you could include some counters at different places in the program
and see, how often each piece is executed in average
then you could write that critical part in assembly
I remember, we did this in CLAX 1-2 decades ago ...
would it be better to use 128-bit-registers ?
in theory they could make a sudoku-processor
dukuso2 wrote:what's the most inner critical loop ?
you could include some counters at different places in the program
and see, how often each piece is executed in average
then you could write that critical part in assembly
I remember, we did this in CLAX 1-2 decades ago ...
would it be better to use 128-bit-registers ?
in theory they could make a sudoku-processor
zhouyundong_2012 wrote:I don't think so.
Research of this code is just starting.
Don't give up.
Update is not the most effecient, Guess is not the most effecint.
C1 = S | FULL_TO_COLUMN(F[0]);
C2 = S | FULL_TO_COLUMN(F[1]);
F[1] &= TblMaskSingle[S] & TblMaskDouble[C1];
F[0] &= TblMaskSingle[S] & TblMaskDouble[C2];
if ((F[26] &= TblComplexMask[Shrink]) == 0) return false;