The SWAP_ macros already write the result to their destination arg, so there's no need for an extra assignment -- and this is undefined behaviour because there are two assignments to the same variable without an intervening sequence point.
GCC 10.2 warns about this when compiling on 32-bit ARM.
The
SWAP_macros already write the result to their destination arg, so there's no need for an extra assignment -- and this is undefined behaviour because there are two assignments to the same variable without an intervening sequence point.GCC 10.2 warns about this when compiling on 32-bit ARM.