It's not clear to me that any compiler can prevent/warn of all run time ram problems like stack overflow or memory heap overflow etc
About the best that could be done, if anything, would be to show how much statically allocated SRAM was in use, at the very start of the program; determining what happens after that would be on-par (or identical, most likely) to "solving the halting problem" (in other words, you could name your price for selling the technology that allowed you to do so, collect the Nobel Prize, and be smug in knowing you were smarter than both Alonzo Church and Alan Turing - AKA "not bloody likely!")...