search for: __strong

...en I AST dump my class I can see the information I need is all there (see the last line): |-ObjCMethodDecl 0x112790f90 <line:32:1, line:34:1> - testAddConcreteDataModel: 'void' | |-ImplicitParamDecl 0x112791960 <<invalid sloc>> self 'DFDataModelContainer *const __strong' | |-ImplicitParamDecl 0x1127919c0 <<invalid sloc>> _cmd 'SEL':'SEL *' | |-ParmVarDecl 0x112791040 <line:32:35, col:55> helpmeh 'DFDemoDataModelOne *__strong' | `-CompoundStmt 0x112791bf0 <col:63, line:34:1> | `-ExprWithCleanups 0x1...

...in general. It seems to me, as Speziale already pointed out, that the OpenCL type qualifiers aren't address space qualifiers at all (in the Embedded C sense). They might be better implemented as a separate set of qualifiers in the way that Objective-C defines its garbage-collection qualifiers, __strong and __weak. See the Qualifiers class in AST/Type.h. > As it is, I hope that backends that do not understand address spaces > at all know to error out when they receive IR that uses address > spaces. This is currently not the case. The back ends for architectures that don't have multi...

Hello Michael, > The module dump suggests everything is right, i can see in the function call the struct with the values 10 and 25, but the function is only received the 10 for the x field, nothing for the y field.  Am I missing something? You're missing the Platform ABI. I assume you're on x86-64, then your struct (according to the ABI) should be passed in a single 64 bit register as

I've been working on a wrapper for LLVM's C++ API to use from Objective-C for a scripting language I'm working on. I currently have an issue with passing arguments to a function that takes a struct argument. typedef struct _test_struct { int x; int y; } test_struct; id testLLVMStructFuncCall(test_struct x) { NSLog(@"%d %d",x.x,x.y); return N(x.x + x.y); }

On Mon, Feb 28, 2011 at 4:41 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > > The more I think about it, the more I become uncomfortable with the > concept of language-specific address spaces in LLVM.  These are the > main issues I see with language-specific address spaces: ... > Instead of language-specific address spaces, each target should > concentrate on

On Fri, Feb 25, 2011 at 02:55:33PM -0500, Ken Dyck wrote: > The address space mechanism is used by some code generators to > differentiate between physical memory spaces. The PIC16 code generator > uses address spaces 0 and 1 to select between its RAM and ROM spaces. > And X86 uses address space 256 for GS and 257 for FS. In the back end > for a dual-harvard DSP that I've been