Displaying 9 results from an estimated 9 matches for "abortprocessact".
2007 Feb 22
0
[LLVMdev] opt -verify
...which also returns false, but does not cause an abort
or report anything to stderr about what caused the verification to fail.
From the doxygen for verifyFunction() and verifyModule(), it seems
like they both should print information to stderr if the verification
fails and should abort opt if AbortProcessAction is passed as parameter.
Is this a bug?
Ryan M. Lefever wrote:
> I followed what you said and called verifyModule() with the
> AbortProcessAction option. verifyModule() returns false, but does not
> abort and does not print out any information about what caused the
> verificat...
2007 Feb 22
3
[LLVMdev] opt -verify
I followed what you said and called verifyModule() with the
AbortProcessAction option. verifyModule() returns false, but does not
abort and does not print out any information about what caused the
verification to fail.
Chris Lattner wrote:
> On Wed, 21 Feb 2007, Ryan M. Lefever wrote:
>> I am writing an interprocedural compiler pass. Because the passneeds
>...
2012 Jun 11
2
[LLVMdev] Why always abort in verifyFunction?
Hello everyone:
I have a little question about the second argument *action* of
verifyFunction.
In docs:
*Enumerator: * *AbortProcessAction*
verifyModule will print to stderr and abort()
*PrintMessageAction*
verifyModule will print to stderr and return true
*ReturnStatusAction*
verifyModule will just return true
But it still abort when I pass PrintMessageAction/ReturnStatusAction
to function.
Log:
Basic Block in...
2007 Feb 22
1
[LLVMdev] opt -verify
...alse, but does not cause an abort
> or report anything to stderr about what caused the verification to fail.
> From the doxygen for verifyFunction() and verifyModule(), it seems
> like they both should print information to stderr if the verification
> fails and should abort opt if AbortProcessAction is passed as parameter.
> Is this a bug?
>
> Ryan M. Lefever wrote:
>
>>I followed what you said and called verifyModule() with the
>>AbortProcessAction option. verifyModule() returns false, but does not
>>abort and does not print out any information about w...
2012 Jun 11
0
[LLVMdev] Why always abort in verifyFunction?
...this, to allow you to not abort if
you so wish.
Joey
On 11 June 2012 09:41, Guowei Xu <myesis at gmail.com> wrote:
> Hello everyone:
>
> I have a little question about the second argument *action* of
> verifyFunction.
>
> In docs:
>
> *Enumerator: * *AbortProcessAction*
>
> verifyModule will print to stderr and abort()
> *PrintMessageAction*
>
> verifyModule will print to stderr and return true
> *ReturnStatusAction*
>
> verifyModule will just return true
>
> But it still abort when I pass
> PrintMessageAction/ReturnSt...
2012 Dec 17
1
[LLVMdev] Execution Engine issue with composite module
...t i think it is peripheral
to the issue
i like all the modules together in a single module called
executableModule. I link them with the method:
Linker::LinkModules(executableModule , moduleToLink,
llvm::Linker::PreserveSource, &errorMsg);
i call
llvm::verifyModule(* executableModule, llvm::AbortProcessAction, &err);
which doesn't seem to find anything wrong with the linked module.
then i proceed to create the executionEngine:
llvm::EngineBuilder eB(executableModule);
eB.setEngineKind(llvm::EngineKind::JIT);
llvmEngine = eB.create();
which seems to go w...
2012 Jun 12
2
[LLVMdev] Why always abort in verifyFunction?
...gt; Joey
>
> On 11 June 2012 09:41, Guowei Xu <myesis at gmail.com> wrote:
>
>> Hello everyone:
>>
>> I have a little question about the second argument *action* of
>> verifyFunction.
>>
>> In docs:
>>
>> *Enumerator: * *AbortProcessAction*
>>
>> verifyModule will print to stderr and abort()
>> *PrintMessageAction*
>>
>> verifyModule will print to stderr and return true
>> *ReturnStatusAction*
>>
>> verifyModule will just return true
>>
>> But it still abort when...
2007 Feb 22
0
[LLVMdev] opt -verify
On Wed, 21 Feb 2007, Ryan M. Lefever wrote:
> I am writing an interprocedural compiler pass. Because the passneeds
> information from a FunctionPass, e.g., the post-dominance frontier
> (PDF), and because a ModulePass is not permitted to require a
> FunctionPass, I am forced to make my pass a FunctionPass and do majority
> of its work in the doFinalization() method.
ok
> When
2007 Feb 22
2
[LLVMdev] opt -verify
I am writing an interprocedural compiler pass. Because the passneeds
information from a FunctionPass, e.g., the post-dominance frontier
(PDF), and because a ModulePass is not permitted to require a
FunctionPass, I am forced to make my pass a FunctionPass and do majority
of its work in the doFinalization() method.
When I run "opt -mypass -verify -o code2.bc code1.bc" I get no