Displaying 16 results from an estimated 16 matches for "setinlineasmdiagnostichandler".
2012 Jun 04
2
[LLVMdev] [llvm-commits] [PATCH] Allow per-thread re-direction of outs()/errs()
...t; not require messing with the process signal handlers. Is there any reason
> to prefer one over the other (thread vs. signal)?
>
> This leaves the following issues:
>
> Why is the error handling stuff in LLVMContext tied to inline asm? The
> error handler setter is even called setInlineAsmDiagnosticHandler. Can we
> make this more generic? I glossed right over the emitError methods the last
> time I read through this stuff because I saw "InlineAsm" everywhere and
> figured it wasn't the right tool for the job! :)
Inline asm is the only place where we have a way of mapping fo...
2013 Jul 21
0
[LLVMdev] [RFC] Add warning capabilities in LLVM.
...aught 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 interfaces to be more generic, add a simple enumeration of whatever diagnostics can be produced from the backend, and add support in clang for mapping those enumeration values to the corresponding clang diagnostics. This would be a small amount of wo...
2012 Jun 04
0
[LLVMdev] [llvm-commits] [PATCH] Allow per-thread re-direction of outs()/errs()
...r handler, which does
not require messing with the process signal handlers. Is there any reason
to prefer one over the other (thread vs. signal)?
This leaves the following issues:
1. Why is the error handling stuff in LLVMContext tied to inline asm?
The error handler setter is even called setInlineAsmDiagnosticHandler.
Can we make this more generic? I glossed right over the emitError methods
the last time I read through this stuff because I saw "InlineAsm"
everywhere and figured it wasn't the right tool for the job! :)
2. As Hal points out, this only covers errors at the moment. Is t...
2013 Jul 17
4
[LLVMdev] [RFC] Add warning capabilities in LLVM.
...rting* warnings into LLVM, we have to thread an interface with sufficient power to express many different concepts.
I don't understand what you are proposing.
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 interfaces to be more generic, add a simple enumeration of whatever diagnostics can be produced from the backend, and add support in clang for mapping those enumeration values to the corresponding clang diagnostics. This would be a small amount of wo...
2012 Jun 03
2
[LLVMdev] [llvm-commits] [PATCH] Allow per-thread re-direction of outs()/errs()
On Sun, 03 Jun 2012 12:12:06 -0700
Chris Lattner <clattner at apple.com> wrote:
>
> On Jun 2, 2012, at 11:01 AM, Mikael Lyngvig wrote:
>
> > If I may add my two cents:
> >
> > I am planning to use LLVM as the backend for a compiler I am
> > working on. And I wholeheartedly agree with Justin that it is a
> > problem, if LLVM is allowed to freely
2012 Jun 04
0
[LLVMdev] [llvm-commits] [PATCH] Allow per-thread re-direction of outs()/errs()
...cess signal handlers. Is there any
> reason
> > to prefer one over the other (thread vs. signal)?
> >
> > This leaves the following issues:
> >
> > Why is the error handling stuff in LLVMContext tied to inline asm? The
> > error handler setter is even called setInlineAsmDiagnosticHandler. Can
> we
> > make this more generic? I glossed right over the emitError methods the
> last
> > time I read through this stuff because I saw "InlineAsm" everywhere and
> > figured it wasn't the right tool for the job! :)
>
> Inline asm is the only place...
2012 Jun 22
2
[LLVMdev] How to generate a non-fatal error from the backend
There are times that I want to generate an ERROR, but not stop processing of the code. An example of this would be when I find there is a value out of range for a specific operand.
producing the error for all instances of this class of errors would be good.
Also, I would like to have the error message have some relationship to the offending source.
Thanks,
Jack
-------------- next part
2013 Jul 22
4
[LLVMdev] [RFC] Add warning capabilities in LLVM.
...n 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 interfaces to be more generic, add a simple enumeration of whatever diagnostics can be produced from the backend, and add support in clang for mapping those enumeration values to the corresponding clang diagnostics. This would be a small amount of wo...
2013 Jul 17
0
[LLVMdev] [RFC] Add warning capabilities in LLVM.
...LLVM, we have to thread an interface with sufficient power to express many different concepts.
>
> I don't understand what you are proposing.
>
> 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 interfaces to be more generic, add a simple enumeration of whatever diagnostics can be produced from the backend, and add support in clang for mapping those enumeration values to the corresponding clang diagnostics. This would be a small amount of wo...
2013 Jul 17
3
[LLVMdev] [RFC] Add warning capabilities in LLVM.
...o thread an interface with sufficient power to express many different concepts.
>>
>> I don't understand what you are proposing.
>>
>> 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 interfaces to be more generic, add a simple enumeration of whatever diagnostics can be produced from the backend, and add support in clang for mapping those enumeration values to the corresponding clang diagnostics. This would be a small amount of wo...
2012 Jun 04
2
[LLVMdev] [llvm-commits] [PATCH] Allow per-thread re-direction of outs()/errs()
...ny
>> > reason
>> > to prefer one over the other (thread vs. signal)?
>> >
>> > This leaves the following issues:
>> >
>> > Why is the error handling stuff in LLVMContext tied to inline asm? The
>> > error handler setter is even called setInlineAsmDiagnosticHandler. Can
>> > we
>> > make this more generic? I glossed right over the emitError methods the
>> > last
>> > time I read through this stuff because I saw "InlineAsm" everywhere and
>> > figured it wasn't the right tool for the job! :)
>>...
2013 Jul 20
0
[LLVMdev] [RFC] Add warning capabilities in LLVM.
...rface with sufficient power to express many different concepts.
>>>
>>> I don't understand what you are proposing.
>>>
>>> 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 interfaces to be more generic, add a simple enumeration of whatever diagnostics can be produced from the backend, and add support in clang for mapping those enumeration values to the corresponding clang diagnostics. This would be a small amount of wo...
2013 Jul 22
0
[LLVMdev] [RFC] Add warning capabilities in LLVM.
...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 interfaces to be more generic, add a simple enumeration of whatever diagnostics can be produced from the backend, and add support in clang for mapping those enumeration values to the corresponding clang diagnostics. This would be a small amount of wo...
2013 Jul 17
0
[LLVMdev] [RFC] Add warning capabilities in LLVM.
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 Needed **
>
> 1. Decide whether or not we want such capabilities (if we do not we may
>
2013 Jul 22
0
[LLVMdev] [RFC] Add warning capabilities in LLVM.
...ions 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 interfaces to be more generic,
> >> add a simple enumeration of whatever diagnostics can be produced
> >> from the backend, and add support in clang for mapping those
> >> enumeration values to the correspondin...
2013 Jul 17
2
[LLVMdev] [RFC] Add warning capabilities in LLVM.
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 Needed **
>>
>> 1. Decide whether or not we want such capabilities (if we do not we may just
>> add sporadically the support for a new warning/group of warning/error).
>> 2. Come