There have been research projects that have attempted to make a standards compliant "safe C" a number of different times. You either end up with a 3x execution

There have been research projects that have attempted to make a standards compliant "safe C" a number of different times. You either end up with a 3x execution time overhead, only support a subset, or break programs that do unsafe type punning. As a result, this is not viable.