search for: avrtargetmachin

...to troubleshoot this problem. I'm trying to write a backend for the AVR. There is an undefined reference at line 48 which is the line FrameInfo() is on. I've tried to use the MSP430 and other targets as references so I'm not sure what changes I did would cause a problem on this line? AVRTargetMachine::AVRTargetMachine(const Target &T, const std::string &TT, const std::string &FS) : LLVMTargetMachine(T, TT), Subtarget(TT, FS), DataLayout("e-p:16:8:8-i8:8:8-i16:8:8-i32:8:8"), InstrInfo(Subtarget), TLInfo(*this), F...

...t;>>> >>>>> * hasDivideInXXXMode >>>>> >>>>> * useSoftFloat (soft-float-point), hasVFP2 >>>>> >>>>> Overrided addIRTranslator, addLegalizeMachineIR, >>>>> addRegBankSelectaddGlobalInstructionSelect in AVRTargetMachine. >>>>> >>>>> Added AVRGenGlobalISel.inc to CMakeLists.txt for tablegen, also *.cpp >>>>> related to GlobalISel. >>>>> >>>>> Also added GlobalISel dependence to LLVMBuild.txt >>>>> >>>>> But tab...

Cool. That explains a lot! Sorry if this is a total n00b question, but… how does the datalayout string get overridden? in llvm/lib/Target/AVR/AVRTargetMachine.cpp I can see the code that determines the default datalayout for AVR… static const char *AVRDataLayout = "e-P1-p:16:8-i8:8-i16:8-i32:8-i64:8-f32:8-f64:8-n8-a:8”; However in the LLVM iR below, the target datalayout was present and didn’t contain “P1”. So (I’m sure i’m not the first person...

That’s useful info, thanks. I think it will be useful for me to understand the connection, why this type of pointer is being emitted now. Do you have any suggestions where i can look to find the platform specific code that is making function pointers go into addrspace? Carl p.s. I am also working on passing the avr target flag to swift, but swift itself had (has?) limitations that make it