search for: mcid

Displaying 20 results from an estimated 45 matches for "mcid".

Did you mean: cid
2015 Aug 12
2
ARM: Predicated returns considered analyzable?
...gt;> this? > > Isn't it because one of the predicates is CPSR, which means it's a > conditional instruction, so not really a terminator? It is marked as a terminator in the table-gen output (ARMGenInstrInfo.inc): { 2399, 5, 1, 4, 355, 0|(1ULL<<MCID::Pseudo)|(1ULL<<MCID::Return)|(1ULL<<MCID::Barrier)|(1ULL<<MCID::MayLoad)|(1ULL<<MCID::Predicable)|(1ULL<<MCID::Terminator)|(1ULL<<MCID::Variadic)|(1ULL<<MCID::UnmodeledSideEffects)|(1ULL<<MCID::ExtraDefRegAllocReq), 0x0ULL, nullptr, nullptr, Operand...
2015 Aug 10
2
ARM: Predicated returns considered analyzable?
Hello, The function ARMBaseInstrInfo::AnalyzeBranch contains the following piece of code: } else if (I->isReturn()) { // Returns can't be analyzed, but we should run cleanup. CantAnalyze = !isPredicated(I); } else { This could lead to cases where for a block that ends with a conditional return, AnalyzeBranch returns false (i.e. analyzed), both TBB and FBB are
2013 Nov 11
0
MCID
Hello Forum, Does any version of asterisk supports Malicious Communication Identification (MCID) using IP standard 3GPP TS 24.616? If yes how can I enable or configure it? Regards Rajib -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20131111/5bf768a4/attachment.html>
2018 Feb 09
2
[X86] MoveImm flag for instructions
Hi, I had (naively?) expected that the instruction to move immediate to register or memory (such as MOV32mi, MOV32ri, MOV64mi32, MOV64ri, MOV64ri32) would be marked with the flag MCID::MovImm via the X86InstrInfo.td (and hence in the generated X86GenInstrInfo.inc). I do not see that to be the case. Can someone please tell me if my expectation is flawed? Is there a better/different way to determine to test for move immediate to register/memory instruction on X86 other that the...
2016 Sep 24
2
RFC: Implement variable-sized register classes
On 9/24/2016 7:20 AM, Alex Bradbury wrote: > My concern is that all of the above adds yet more complexity to what > is already (in my view) a fairly difficult part of LLVM to understand. > The definition of MyRegisterClass is not so bad though, and perhaps it > doesn't matter how it works under the hood to the average backend > writer. I agree with the complexity, but I would
2012 Dec 01
0
[LLVMdev] BuildMI declarations inconsistency?
...or null or anything and I didn't see any potential declaration conflicts. Am I missing something? Is there a reason for this? inline MachineInstrBuilder BuildMI(MachineBasicBlock *BB, DebugLoc DL, const MCInstrDesc &MCID) { return BuildMI(*BB, BB->end(), DL, MCID); } inline MachineInstrBuilder BuildMI(MachineBasicBlock *BB, DebugLoc DL, const MCInstrDesc &MCID, unsigned DestReg) { return BuildMI...
2018 Feb 09
2
[X86] MoveImm flag for instructions
...Yadavalli via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi, >> >> I had (naively?) expected that the instruction to move immediate to >> register or memory (such as MOV32mi, MOV32ri, MOV64mi32, MOV64ri, >> MOV64ri32) would be marked with the flag MCID::MovImm via the >> X86InstrInfo.td (and hence in the generated X86GenInstrInfo.inc). >> >> I do not see that to be the case. >> >> Can someone please tell me if my expectation is flawed? Is there a >> better/different way to determine to test for move immediate t...
2018 Feb 09
0
[X86] MoveImm flag for instructions
...18 at 11:45 AM, S. Bharadwaj Yadavalli via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > I had (naively?) expected that the instruction to move immediate to > register or memory (such as MOV32mi, MOV32ri, MOV64mi32, MOV64ri, > MOV64ri32) would be marked with the flag MCID::MovImm via the > X86InstrInfo.td (and hence in the generated X86GenInstrInfo.inc). > > I do not see that to be the case. > > Can someone please tell me if my expectation is flawed? Is there a > better/different way to determine to test for move immediate to > register/memory i...
2013 Feb 27
1
[LLVMdev] Instruction scheduling barrier
I found myself wanting a "scheduling barrier" in LLVM. In my specific circumstances I only want it to mean that TargetInstrInfoImpl::isSchedulingBoundary() would return true. I added SchedulingBarrier to MCID in MCInstrDesc.h and pushed it through TD attributes down to isSchedulingBoundary(). Is this something of general interest, or is there another mechanism for implementing barriers that I missed? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://li...
2018 Feb 09
0
[X86] MoveImm flag for instructions
...>> llvm-dev at lists.llvm.org> wrote: >> >>> Hi, >>> >>> I had (naively?) expected that the instruction to move immediate to >>> register or memory (such as MOV32mi, MOV32ri, MOV64mi32, MOV64ri, >>> MOV64ri32) would be marked with the flag MCID::MovImm via the >>> X86InstrInfo.td (and hence in the generated X86GenInstrInfo.inc). >>> >>> I do not see that to be the case. >>> >>> Can someone please tell me if my expectation is flawed? Is there a >>> better/different way to determine to t...
2012 Aug 21
8
[LLVMdev] Let's get rid of neverHasSideEffects
All, TableGen likes to infer the MCID::UnmodeledSideEffects flag from an instruction's pattern. When an instruction doesn't have a pattern, it is assumed to have side effects. It's possible to override this behavior by setting neverHasSideEffects = 1. It was originally the intention that most instructions have patterns, b...
2011 Oct 01
0
[LLVMdev] mayload and maystore?
...use in TD files. /// mayLoad - Return true if this instruction could possibly read memory. /// Instructions with this flag set are not necessarily simple load /// instructions, they may load a value and modify it, for example. bool mayLoad() const { return Flags & (1 << MCID::MayLoad); } /// mayStore - Return true if this instruction could possibly modify memory. /// Instructions with this flag set are not necessarily simple store /// instructions, they may store a modified value based on their operands, or /// may not actually modify anything, for e...
2012 Aug 21
0
[LLVMdev] Let's get rid of neverHasSideEffects
On Aug 21, 2012, at 2:02 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote: > All, > > TableGen likes to infer the MCID::UnmodeledSideEffects flag from an instruction's pattern. When an instruction doesn't have a pattern, it is assumed to have side effects. Hi Jakob, I don't understand what you're saying. Are you proposing that all properties (may load, store, side effects) be explicitly added to...
2005 Jun 28
1
AVM CAPI INSTALLATION
...00 0200 39000000 1f010040 1b0b0000 bf000080 00000000 00000000 00000000 00000000 00000000 00000000 01000001 00020000 00000000 00000000 00000000 Supplementary services support: 0x000003ff Hold / Retrieve Terminal Portability ECT 3PTY Call Forwarding Call Deflection MCID CCBS But if I call to asterisk even if asterisk isn't start, it's busy,I dont unsderstand Help me
2013 Feb 15
2
[LLVMdev] build a machine instruction by itself
...ldMi forms. To me, creating a MachineInstr is not related this context of how you are placing 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(Ma...
2015 Aug 25
2
[LLVMdev] TableGen Register Class not matching for MI in 3.6
...mp;& > "Chain and glue operands should occur at end of operand list!"); > // Get/emit the operand. > unsigned VReg = getVR(Op, VRBaseMap); > assert(TargetRegisterInfo::isVirtualRegister(VReg) && "Not a vreg?"); > const MCInstrDesc &MCID = MIB->getDesc(); > bool isOptDef = IIOpNum < MCID.getNumOperands() && > MCID.OpInfo[IIOpNum].isOptionalDef(); > // If the instruction requires a register in a different class, create > // a new virtual register and copy the value into it, but first attempt to &g...
2015 Aug 25
2
[LLVMdev] TableGen Register Class not matching for MI in 3.6
..."Chain and glue operands should occur at end of operand list!"); >> // Get/emit the operand. >> unsigned VReg = getVR(Op, VRBaseMap); >> assert(TargetRegisterInfo::isVirtualRegister(VReg) && "Not a vreg?"); >> const MCInstrDesc &MCID = MIB->getDesc(); >> bool isOptDef = IIOpNum < MCID.getNumOperands() && >> MCID.OpInfo[IIOpNum].isOptionalDef(); >> // If the instruction requires a register in a different class, create >> // a new virtual register and copy the value into it, but fir...
2015 Aug 25
4
[LLVMdev] TableGen Register Class not matching for MI in 3.6
..."Chain and glue operands should occur at end of operand list!"); >> // Get/emit the operand. >> unsigned VReg = getVR(Op, VRBaseMap); >> assert(TargetRegisterInfo::isVirtualRegister(VReg) && "Not a vreg?"); >> const MCInstrDesc &MCID = MIB->getDesc(); >> bool isOptDef = IIOpNum < MCID.getNumOperands() && >> MCID.OpInfo[IIOpNum].isOptionalDef(); >> // If the instruction requires a register in a different class, create >> // a new virtual register and copy the value into it, but fir...
2013 Feb 16
0
[LLVMdev] build a machine instruction by itself
...eInstr is not related this context of how you > are placing 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 > &g...
2015 Aug 24
2
[LLVMdev] TableGen Register Class not matching for MI in 3.6
> On Aug 24, 2015, at 1:30 PM, Ryan Taylor <ryta1203 at gmail.com> wrote: > > I'm trying to do something like this: > > // Dst = NewVReg's reg class > // *II = MCInstrDesc > // IIOpNum = II Operand Num > > if (TRI->getCommonSubClass(DstRC, TRI->getRegClass(II->OpInfo[IIOpNum].RegClass)) == DstRC) > MRI->setRegClass(VReg, DstRC); >