search for: targetcallingconv

Attached is a working patch set for llvm to be able to emit arm64 (currently as triple aarch64-apple-ios) mach-o object files, in case someone is interested. I'm not sure if the llvm maintainers want the patch given the previous message that there's going to be an official patch set from apple to support this, but here is mine. What works (tested on an iPhone 5S): * objc strings,

...vector parameters? > > define internal fastcc <4 x float> @add(<4 x float> %a.val, <4 x float> > %b.val) nounwind { > entry: > %tmp4 = fadd <4 x float> %a.val, %b.val > ret <4 x float> %tmp4 > } That I don't know, but I'd look around TargetCallingConv.td, CallingConvLower.h, etc. -K -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation

...y just a starting register to assign to for the CallingConv class and > then have it just use sequential registers? No; you'll have to hack it to deal with an infinite register file. The relevant bits are include/llvm/CallingConvLower.h, utils/TableGen/CallingConvEmitter.cpp, and lib/Target/TargetCallingConv.td. None of the current LLVM targets using CodeGen have infinite registers. Although, what exactly is the calling convention? Are the arguments supposed to be in registers r0-rN, where N is the number of arguments? Or is there some way of specifying which registers to pass? Where does the call...

How about vector parameters? define internal fastcc <4 x float> @add(<4 x float> %a.val, <4 x float> %b.val) nounwind { entry: %tmp4 = fadd <4 x float> %a.val, %b.val ret <4 x float> %tmp4 } a and b are flattened by SelectionDAGISel::LowerArguments(const BasicBlock *LLVMBB) before letting the target handle it. SDValue NewRoot =

With my backend code gen I want to assign calling parameters to a list of registers, but since I'm targeting a virtual instruction set. I don't want to be limited by the number of registers. Is there a way using TableGen to specify just a starting register to assign to for the CallingConv class and then have it just use sequential registers? Micah Villmow Systems Engineer Advanced

...ude/llvm/Target/Target.td -- Installing: /usr/local/llvm-2.8/include/llvm/Target/TargetAsmBackend.h -- Installing: /usr/local/llvm-2.8/include/llvm/Target/TargetAsmLexer.h -- Installing: /usr/local/llvm-2.8/include/llvm/Target/TargetAsmParser.h -- Installing: /usr/local/llvm-2.8/include/llvm/Target/TargetCallingConv.h -- Installing: /usr/local/llvm-2.8/include/llvm/Target/TargetCallingConv.td -- Installing: /usr/local/llvm-2.8/include/llvm/Target/TargetData.h -- Installing: /usr/local/llvm-2.8/include/llvm/Target/TargetELFWriterInfo.h -- Installing: /usr/local/llvm-2.8/include/llvm/Target/TargetFrameInfo.h --...

On Thu, Sep 30, 2010 at 3:08 PM, Samuel Williams <space.ship.traveller at gmail.com> wrote: > Hi, > > I might just be doing something stupid, but when I do > > $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. > $ sudo make install > > I don't get the expected headers in >        /usr/local/llvm-2.8/include/llvm > > It is

Hi, I might just be doing something stupid, but when I do $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. $ sudo make install I don't get the expected headers in /usr/local/llvm-2.8/include/llvm It is simply an empty directory. What am I doing wrong? This is on Mac OS X, CMake 2.8+ Kind regards, Samuel