Probaly not part of this bug, but I just noticed that buildOpAssign also calls semantic3 immediately. Does it have the same problem as the buildXopXXX functions?