search for: getnumregisters

...0x0000000100429633 llvm::TargetLowering::getRegisterType(llvm::LLVMContext&, llvm::EVT) const + 208419 8 llc 0x000000010042aab6 llvm::TargetLowering::getRegisterType(llvm::LLVMContext&, llvm::EVT) const + 213670 9 llc 0x00000001004f9474 llvm::TargetLowering::getNumRegisters(llvm::LLVMContext&, llvm::EVT) const + 13556 10 llc 0x00000001004face4 llvm::TargetLowering::getNumRegisters(llvm::LLVMContext&, llvm::EVT) const + 19812 11 llc 0x00000001004fb2e2 llvm::TargetLowering::getNumRegisters(llvm::LLVMContext&, llvm::EVT) const + 21...

...0x0000000100429633 llvm::TargetLowering::getRegisterType(llvm::LLVMContext&, llvm::EVT) const + 208419 8 llc 0x000000010042aab6 llvm::TargetLowering::getRegisterType(llvm::LLVMContext&, llvm::EVT) const + 213670 9 llc 0x00000001004f9474 llvm::TargetLowering::getNumRegisters(llvm::LLVMContext&, llvm::EVT) const + 13556 10 llc 0x00000001004face4 llvm::TargetLowering::getNumRegisters(llvm::LLVMContext&, llvm::EVT) const + 19812 11 llc 0x00000001004fb2e2 llvm::TargetLowering::getNumRegisters(llvm::LLVMContext&, llvm::EVT) const + 21...

[snip] > The ABI boundary lowering requires types to be broken down further into > 'legal types' that can be mapped to registers. The secondary breakdown is > currently handled by TargetLowering::LowerCallTo() calling > getRegisterType() and getNumRegisters(). Most ABIs are defined in terms > of C types, not LLVM IR types, so there is a close connection between the C > frontend and the ABI lowering code in the instruction selector. It would be > a good idea to have the ABI lowering code work independently of the type > system used during i...

...for this one) that lowers pointer operations to integers. > The ABI boundary lowering requires types to be broken down further into 'legal types' that can be mapped to registers. The secondary breakdown is currently handled by TargetLowering::LowerCallTo() calling getRegisterType() and getNumRegisters(). Most ABIs are defined in terms of C types, not LLVM IR types, so there is a close connection between the C frontend and the ABI lowering code in the instruction selector. It would be a good idea to have the ABI lowering code work independently of the type system used during instruction selection...

...all the integer, floating point, and vector types from LLVM IR. The ABI boundary lowering requires types to be broken down further into 'legal types' that can be mapped to registers. The secondary breakdown is currently handled by TargetLowering::LowerCallTo() calling getRegisterType() and getNumRegisters(). Most ABIs are defined in terms of C types, not LLVM IR types, so there is a close connection between the C frontend and the ABI lowering code in the instruction selector. It would be a good idea to have the ABI lowering code work independently of the type system used during instruction selection...