Displaying 10 results from an estimated 10 matches for "noimp".
Did you mean:
nimp
2011 Aug 15
0
Stopping criterion in option "control" of BBsolve( )
Dear Dr. Gilbert, Dr. Varadhan and all R-help list members,
I'm using the function BBsolve( ) and I have some questions on the stopping
criterion "maxit" and "noimp" specified in the option "control". Here
are two such examples I'm having problem with. In these two examples, the
function BBsolve( ) always stops at iteration 100, overlooking the values I
specified in "control".
Any advise are greatly appreciated!
Sincerely...
2010 Aug 27
2
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
...e of TCRETURNri64 and RET should be created.
> I have sources of rev.112200.
>
> Here is the stack when TCRETURNri64 instruction is created:
> #1 0x0000000802c8b4e2 in llvm::MachineFunction::CreateMachineInstr
> (this=0x30eb000, TID=@0x803a78940, DL={LineCol = 0, ScopeIdx = 0},
> NoImp=false) at /tmp/llvm-svn/llvm/lib/CodeGen/MachineFunction.cpp:153
> #2 0x00000008028ea45b in llvm::BuildMI (BB=@0x4b69378,
> I={<std::iterator<std::bidirectional_iterator_tag, llvm::MachineInstr,
> long int, llvm::MachineInstr*, llvm::MachineInstr&>> = {<No data
> fi...
2010 Aug 27
0
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
...t;
As I understand only one of TCRETURNri64 and RET should be created.
I have sources of rev.112200.
Here is the stack when TCRETURNri64 instruction is created:
#1 0x0000000802c8b4e2 in llvm::MachineFunction::CreateMachineInstr
(this=0x30eb000, TID=@0x803a78940, DL={LineCol = 0, ScopeIdx = 0},
NoImp=false) at /tmp/llvm-svn/llvm/lib/CodeGen/MachineFunction.cpp:153
#2 0x00000008028ea45b in llvm::BuildMI (BB=@0x4b69378,
I={<std::iterator<std::bidirectional_iterator_tag, llvm::MachineInstr,
long int, llvm::MachineInstr*, llvm::MachineInstr&>> = {<No data
fields>}, NodePtr...
2010 Aug 27
3
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On Aug 27, 2010, at 11:00 AMPDT, Eric Christopher wrote:
>>>
>>> For some reason I am getting this error even when I only have an
>>> empty 'main' function. So I couldn't create .ll file reproducing
>>> it and I have to debug myself.
>>>
>>> The function causing the problem is stub created in
>>> JIT::runFunction:
2013 Feb 15
2
[LLVMdev] build a machine instruction by itself
...it.
So I guess I could use:
/// CreateMachineInstr - Allocate a new MachineInstr. Use this instead
/// of `new MachineInstr'.
///
MachineInstr *CreateMachineInstr(const MCInstrDesc &MCID,
DebugLoc DL,
bool NoImp = false);
so my creator function needs to at least have a parameter of type
MachineFunction
I can get the MachineFunction from any MachineBasicBlock using getParent
MachineInstr BuildAddiuSpImm(MachineFunction &MF, int64_t Imm) const;
I did not want to have to pass any more arguments tha...
2010 Aug 27
0
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
...T should be created.
>> I have sources of rev.112200.
>>
>> Here is the stack when TCRETURNri64 instruction is created:
>> #1 0x0000000802c8b4e2 in llvm::MachineFunction::CreateMachineInstr
>> (this=0x30eb000, TID=@0x803a78940, DL={LineCol = 0, ScopeIdx = 0},
>> NoImp=false) at /tmp/llvm-svn/llvm/lib/CodeGen/MachineFunction.cpp:
>> 153
>> #2 0x00000008028ea45b in llvm::BuildMI (BB=@0x4b69378,
>> I={<std::iterator<std::bidirectional_iterator_tag,
>> llvm::MachineInstr,
>> long int, llvm::MachineInstr*, llvm::MachineInstr&am...
2013 Feb 16
0
[LLVMdev] build a machine instruction by itself
...> /// CreateMachineInstr - Allocate a new MachineInstr. Use this instead
> /// of `new MachineInstr'.
> ///
> MachineInstr *CreateMachineInstr(const MCInstrDesc &MCID,
> DebugLoc DL,
> bool NoImp = false);
>
> so my creator function needs to at least have a parameter of type
> MachineFunction
> I can get the MachineFunction from any MachineBasicBlock using getParent
>
> MachineInstr BuildAddiuSpImm(MachineFunction &MF, int64_t Imm) const;
>
> I did not want to...
2010 Aug 27
2
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
...at these addresses were reused and the second MIs created at these
particular addressed are of interest, not the first ones.
RET creation stack (created first):
#1 0x0000000802c8b4e2 in llvm::MachineFunction::CreateMachineInstr
(this=0x30eb000, TID=@0x803a99240, DL={LineCol = 0, ScopeIdx = 0},
NoImp=false) at /tmp/llvm-svn/llvm/lib/CodeGen/MachineFunction.cpp:153
#2 0x00000008028ea45b in llvm::BuildMI (BB=@0x4b69378,
I={<std::iterator<std::bidirectional_iterator_tag, llvm::MachineInstr,
long int, llvm::MachineInstr*, llvm::MachineInstr&>> = {<No data
fields>}, NodePtr...
2013 Feb 15
0
[LLVMdev] build a machine instruction by itself
On Feb 15, 2013, at 1:21 PM, Reed Kotler <rkotler at mips.com> wrote:
> I want to have some functions that create machine instructions, not specifying which machine function or basic block or iterator they are part of.
All machine instructions must be created by a machine function. It provides the context for memory allocation etc.
> And then I want to use that result when adding
2013 Feb 15
2
[LLVMdev] build a machine instruction by itself
I want to have some functions that create machine instructions, not
specifying which machine function or basic block or iterator they are
part of. And then I want to use that result when adding that instruction
to a basic block.
I'm pretty sure you can do this but we have not done this in the Mips
port so far. We just use instruction builder.
Anyone know how to do this best, or can point