search for: diagnosticinfooptimizationbase

...emitting diagnostic info, where one of the parameters was the severity level (llvm::DiagnosticSeverity). I'm particularly interested in drawing a distinction between "remarks" (which should be optionally filtered) and "warnings" (which should always be sent to errs()) The DiagnosticInfoOptimizationBase supports the exact set of details I care about. Unfortunately it's an abstract class, which is why I'm in my current situation. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150624/b5795748/attachm...

...t;< setExtraArgs() << " in favor of " << NV("InfavorOfValue", AvailableValue); }); There is some C++ magic going on behind the scenes here, and it makes for a nice interface, but I'm not clear about what ends up being stored where. I think within DiagnosticInfoOptimizationBase all the string parts of this get stored in a vector of name-value pairs with the unnamed strings just having an empty name. At some point, I guess this gets assembled into a single string? I've also found references to string tables for the bitstream serializer and a YAML format that uses a str...

Hi all, Is there a good way to add out-of-LLVM-source subclasses, without modifying the corresponding in-source "Kind" enumeration? As I play around with writing an AA pass, I'd like a good way to issue warnings for cases where my AA pass can't handle a particular IR construct. I was thinking to report those warnings via *llvm::LLVMContext::diagnose( const DiagnosticInfo &

Patch for review. On Mon, Aug 21, 2017 at 11:45 PM Puyan Lotfi <puyan.lotfi.llvm at gmail.com> wrote: > Ping. > > Still working on preparing code for review. Will have a patch for review > ready in the coming days. > > PL > > On Tue, Aug 15, 2017 at 12:06 PM Puyan Lotfi <puyan.lotfi.llvm at gmail.com> > wrote: > >> Hi, >> >> >>