From: robfi680@gmail.com   
      
   Semi-unaligned memory tradeoff. If unaligned access is required, the   
   memory logic just increments the physical address by 64 bytes to fetch   
   the next cache line. The issue with this is it does not go backwards to   
   get the address fetched again from the TLB. Meaning no check is made for   
   protection or translation of the address.   
      
   It would be quite slow to have the instructions reissued and percolate   
   down the cache access again.   
      
   This should only be an issue if an unaligned access crosses a memory   
   page boundary.   
      
   The instruction causes an alignment fault if a page cross boundary is   
   detected.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)