title: Migrating from big to little endian: How to predetermine problematic code?
body: <p>I am about to migrate a small project of C code (30+ kSLOC) from a 32-bit big to a 32-bit little endian platform.  I would like to check ante festum, how much work this will be, so I would like to spot code that relies on the original endianess.</p>
  <p>I am looking for an as comprehensive as possible collection of C code idioms, which are depending on big endian.  Do not bother with the effort needed to detect the use of such idioms in real code, I have some code analysis tool support available.</p>