> (Let's focus on location info and representative returns in this > subthread.) > > AFAIU, a return statement may be chosen as a representative return for a > function. The representative return's location is set to > UNKNOWN_LOCATION, because otherwise the results of coverage analysis are > skewed. What is the difficulty preventing us from having both the > location info for the return and faithful coverage?
That's simply impossible since you merge two instructions with different locations into a single one. But the return location should be on the goto. -- Eric Botcazou
