https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87488
--- Comment #7 from David Malcolm <dmalcolm at gcc dot gnu.org> --- I'm unconvinced that doing it for filenames is a good idea (based on the objections in comment #3), but I think that there could be other good uses tagging URLs into the output. For example, a static analysis plugin that emits e.g.: error: NULL pointer 'p' passed as argument 1 to 'foo' [CWE-690] might want to tag the "CWE-690" in the message/metadata with the URL https://cwe.mitre.org/data/definitions/690.html Similarly, any time we mention a GCC option, perhaps we could provide a URL to the documentation of that option on the GCC website. (Sadly, most of our options don't have good URLs)
