title: Compiling an application for use in highly radioactive environments
body: <p>We are compiling an embedded C++ application that is deployed in a shielded device in an environment bombarded with <a href="https://en.wikipedia.org/wiki/Ionizing_radiation" rel="noreferrer">ionizing radiation</a>. We are using GCC and cross-compiling for ARM. When deployed, our application generates some erroneous data and crashes more often than we would like. The hardware is designed for this environment, and our application has run on this platform for several years.</p>
  <p>Are there changes we can make to our code, or compile-time improvements that can be made to identify/correct <a href="https://en.wikipedia.org/wiki/Soft_error" rel="noreferrer">soft errors</a> and memory-corruption caused by <a href="https://en.wikipedia.org/wiki/Single_event_upset" rel="noreferrer">single event upsets</a>? Have any other developers had success in reducing the harmful effects of soft errors on a long-running application?</p>