optimise implementation

[matpalm]

po2

• i'm 90% sure the way i've done the po2 multiply, especially w.r.t using single bits in memory for is_negative etc, could be done in a much more effecient way. it feels wrong to optimise something to the level of shift operators, but require a lookup for the value to shift by ( maybe i'm missing something re: compilation etc )
  • note: an extreme value of this could be writing specific modules per multiply with the shift and ( possible negation ) logic built in...

qb

• in the qb_ network we have >50% free cycles, but not many free multiple DSPs. so how best to restructure the modules so the same module can be clocked twice with different sets of weights?