search for: 2c684258

It seems like a difficult thing to do since we would have to keep metadata intact across transformations, which, AFAIK, is not done. mem2reg, for example, doesn't even propagate debug metadata to phi nodes, and I'm not really sure if it's valid to do so. Also, line information alone seems to be insufficient for providing accurate warnings. Debug metadata does contain variable names,

...or example). I'm thinking of making the optimization passes help the front-end(s), the same way PGO helps the optimization passes. cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131109/2c684258/attachment.html>

Hi all, I was discussing this with a few folks at the dev meeting and it would be interesting for some passes to print some warnings on a later stage than the front-end, in special cases, especially if line information is kept and available at that stage. Is this possible today? My main concern is not correctness, that should have been taken care by the front-end and the sanitizers, but things