search for: inlineasmdiagnostichandler

> IMO, the right way to build this is something like > "InlineAsmDiagnosticHandler" in LLVMContext (but hopefully better, and more > structured :) Hey Chris, Did you catch my suggestion in reply to Hal, about maybe generalizing Clang's diagnostics infrastructure up into LLVM? Your reply seems along the same lines. It seems like a natural fit to reuse that rather tha...

...ut I think that we should start discussing the interfaces. > >> and should probably directly take a Value *, BasicBlock *, Function *, etc. so that the frontend can do the appropriate mapping for the user. >> > > +1 IMO, the right way to build this is something like "InlineAsmDiagnosticHandler" in LLVMContext (but hopefully better, and more structured :). The basic jist of it is that the backend can push messages up, and the frontend can register its hooks to render them however it likes. In this case, I agree that clang "Notes" or some new "informational" diag...

On Nov 26, 2012, at 3:46 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > In my opinion, what we really need is an interface that the frontend can use to get information from the backend optimizers. Then the frontend can display this information to users in an appropriate way. I agree. > Furthermore, this information should be structured (we already have a YAML parser, so that

On Mon, Nov 26, 2012 at 6:26 PM, Sean Silva <silvas at purdue.edu> wrote: >> IMO, the right way to build this is something like >> "InlineAsmDiagnosticHandler" in LLVMContext (but hopefully better, and more >> structured :) > > Hey Chris, > > Did you catch my suggestion in reply to Hal, about maybe generalizing > Clang's diagnostics infrastructure up into LLVM? Your reply seems > along the same lines. It seems like a natu...