I hope this was added as a peculiar historical artifact from 1991, not a statement of how to best write code today. These tricks don't work with GCC 4.1+ and i

I hope this was added as a peculiar historical artifact from 1991, not a statement of how to best write code today. These tricks don't work with GCC 4.1+ and i86_64. For example, in the loop section, the good trick now is to make your code accessible by the GCC vectorizer. If you turn on -fdump-tree-vect-details in GCC, you will see - for every loop - the weighting factors applied and what might have blocked the vectorizer's operation. Vectorized computing existed in 1991 - heck, 1969 - but was not commodity like today.