On 09/30/16 05:22, Rainer Orth wrote:
While this would take care of the testsuite failures, this creates a terrible user experience outside of the testsuite: if we know that -fprofile-arcs -ftest-coverage cannot work on targets without constructor priority support, the compiler should error out with an appropriate message instead of just creating confusing non-working executables.
It should either 1) emit a non-prioritized static ctor 2) or use the older atexit mechanism.
