[PATCH] Add warning capabilities in LLVM (backend part), Take 2

Tobias Grosser tobias at grosser.es
Wed Dec 18 12:19:41 PST 2013

On 12/18/2013 09:15 PM, Tobias Grosser wrote:
> On 12/18/2013 06:34 PM, Quentin Colombet wrote:
>> On Dec 18, 2013, at 2:57 AM, Tobias Grosser <tobias at grosser.es> wrote:
>>> On 12/16/2013 06:41 PM, Quentin Colombet wrote:
>>>> Hi Tobias,
>>>> On Dec 14, 2013, at 1:20 AM, Tobias Grosser <tobias at grosser.es> wrote:
>>> I also used this interface to implement the first diagnostic in Polly
>>> (r197558).
>>> I also saw you started to submit patches to clang. For plugin
>>> authors, it would be amazing if a frontend could optionally register
>>> a callback that demangels function names. Like this, the plugin
>>> default printers could return something sensible.
>> Yes, we have to figure out how to do that.
> This file seems interesting:
> compiler-rt/lib/sanitizer_common/sanitizer_symbolizer_itanium.cc
> It seems there is a demangler already accessible in modern C++ ABI
> libraries. What about providing a demangling interface that uses the C++
> itanium demangler as default (if available), falls back to just return
> the function name if no demangler is available and finally allows the
> frontend to provide its own demangler?

There is also a demangler in libcxxabi that we could copy.

I personally would prefer to use the sanitizer approach of just using 
the platform demangler by default. If a front-end cares, it could still 
provide something better. What do you think?


More information about the llvm-commits mailing list