Displaying 5 results from an estimated 5 matches for "printdiagnost".
Did you mean:
printdiagnostic
2013 Jul 22
4
[LLVMdev] [RFC] Add warning capabilities in LLVM.
...ndler (and we should have a default handler) can be
passed in from the printer of the message (the frontend in the case
provided) and it can be called on the error message. Absolutely this
should be done via the LLVMContext to deal with the case of parallel
function passes.
class Handler {
void printDiagnostic(const char *Message, Location Loc);
};
(Note that I didn't say this was a fleshed out design ;) I think I
prefer the latter to the former and we'd just need an "diagnostic
callback handler" on the context. Though we would need to keep a set
of diagnostics that the backend handl...
2013 Jul 21
0
[LLVMdev] [RFC] Add warning capabilities in LLVM.
Sorry, just getting caught up on an old thread. I haven't been involved in discussions of this.
On Jul 17, 2013, at 8:53 AM, Bob Wilson <bob.wilson at apple.com> wrote:
> First, let me try to clarify my proposal, in case there was any confusion about that. LLVMContext already has a hook for diagnostics, setInlineAsmDiagnosticHandler() et al. I was suggesting that we rename those
2013 Jul 22
0
[LLVMdev] [RFC] Add warning capabilities in LLVM.
...t handler) can be
> passed in from the printer of the message (the frontend in the case
> provided) and it can be called on the error message. Absolutely this
> should be done via the LLVMContext to deal with the case of parallel
> function passes.
>
> class Handler {
> void printDiagnostic(const char *Message, Location Loc);
> };
>
> (Note that I didn't say this was a fleshed out design ;) I think I
> prefer the latter to the former and we'd just need an "diagnostic
> callback handler" on the context. Though we would need to keep a set
> of diag...
2013 Jul 22
0
[LLVMdev] [RFC] Add warning capabilities in LLVM.
...handler) can be
> passed in from the printer of the message (the frontend in the case
> provided) and it can be called on the error message. Absolutely this
> should be done via the LLVMContext to deal with the case of parallel
> function passes.
>
> class Handler {
> void printDiagnostic(const char *Message, Location Loc);
> };
>
> (Note that I didn't say this was a fleshed out design ;) I think I
> prefer the latter to the former and we'd just need an "diagnostic
> callback handler" on the context. Though we would need to keep a set
> of diag...
2013 Jul 17
4
[LLVMdev] [RFC] Add warning capabilities in LLVM.
On Jul 17, 2013, at 2:12 AM, Chandler Carruth <chandlerc at google.com> wrote:
> On Tue, Jul 16, 2013 at 9:34 PM, Bob Wilson <bob.wilson at apple.com> wrote:
>
> On Jul 16, 2013, at 5:51 PM, Eli Friedman <eli.friedman at gmail.com> wrote:
>
>> On Tue, Jul 16, 2013 at 5:21 PM, Quentin Colombet <qcolombet at apple.com> wrote:
>>> ** Advices