tree 52274f4900cf5d4f0f1d61ee59ca474b2a61d4a2
parent 695a34654ab43f1f0b2e42cfde2f51b21a7e4de7
author Gilles Peskine <Gilles.Peskine@arm.com> 1539364534 +0200
committer Gilles Peskine <Gilles.Peskine@arm.com> 1539369172 +0200

Fix likely-harmless undefined behavior surrounding volatile

The code was making two unsequenced reads from volatile locations.
This is undefined behavior. It was probably harmless because we didn't
care in what order the reads happened and the reads were from ordinary
memory, but UB is UB and IAR8 complained.