search for: unsiz

Hi all, Attached is a simple patch that adds a more specific error when you have an unsized type in a gep. Turns $ echo "@g = global i64 ptrtoint(%C* getelementptr(%C* null, i32 1) to i64)" | opt -S opt: <stdin>:1:30: error: invalid indices for getelementptr @g = global i64 ptrtoint(%C* getelementptr(%C* null, i32 1) to i64) into $ echo "@g = global i64 ptrtoin...

To reiterate what I said on IRC, I agree with David and would expect the verifier to reject unsized loads and stores. On Mon, May 30, 2016 at 4:05 PM Sanjoy Das via llvm-dev < llvm-dev at lists.llvm.org> wrote: > This came up in D20764, this IR verifies today: > > %X = type opaque > > define void @f_0(%X* %ptr) { > %t = load %X, %X* %ptr > ret void > } > &...

This came up in D20764, this IR verifies today: %X = type opaque define void @f_0(%X* %ptr) { %t = load %X, %X* %ptr ret void } define void @f_1(%X %val, %X* %ptr) { store %X %val, %X* %ptr ret void } which I found surprising -- what does it mean to load / store values of unknown sizes? Passing it to llc fails an assertion. Are there legitimate cases where we'd want to generate

...ar41 at yahoo.com>> Date: Tuesday, 20 August, 2013 9:32 AM To: LLVM List <llvmdev at cs.uiuc.edu<mailto:llvmdev at cs.uiuc.edu>> Subject: [LLVMdev] Trying to run qt app compiled to bit code Assertion failed: (Ty->isSized() && "Cannot getTypeInfo() on a type that is unsized!") Hi, I am trying to run a simple qt 5 application compiled to bitcode on OS X. I am getting the following error. I have modified lli to load qt libraries. When I use with option mcjit, I get the following error lli -use-mcjit -debug-ir bitcodetestqtapp Assertion failed: (Ty->isSized...

Consider the following test case: %struct.A = type opaque @g = external global [0 x %struct.A] declare void @foo(%struct.A*) define void @f() uwtable ssp align 64 { %x = getelementptr [0 x %struct.A]* @g, i32 0, i32 0 call void @foo(%struct.A* %x) ret void } Before the type system rewrite, we would accept this construct; now, we reject it. (This leads to clang/opt crashing on certain

...on compiled to bitcode on OS X. I am getting the following error. I have modified lli to load qt libraries. When I use with option mcjit, I get the following error lli -use-mcjit -debug-ir bitcodetestqtapp Assertion failed: (Ty->isSized() && "Cannot getTypeInfo() on a type that is unsized!"), function getTypeSizeInBits, file /Users/shailesh/repos/llvm/include/llvm/IR/DataLayout.h, line 449. 0  lli               0x0000000102244f3e llvm::sys::PrintStackTrace(__sFILE*) + 46 1  lli               0x000000010224524b PrintStackTraceSignalHandler(void*) + 27 2  lli               0x00...

...ype of the Values, but if I have still some unused instructions , I can't keep track on them. I try to convert them to Value and get the type or simply get the type of instruction, but have the following error: Assertion `Ty->isSized() && "Cannot getTypeInfo() on a type that is unsized!"' failed. This is second or instruction: %1 = or i32 10, 20 %2 = or i32 %1, 10 ret i32 %1 What can be done in this case? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170721/6ec913d1/att...

...te->Const.MaxClipPlanes); > + } else if (strcmp("gl_CullDistance", name) == 0 > + && size > state->Const.MaxClipPlanes) { > + /* From the ARB_cull_distance spec: > + * > + * "The gl_CullDistance array is predeclared as unsized and > + * must be sized by the shader either redeclaring it with > + * a size or indexing it only with integral constant > + * expressions. The size determines the number and set of > + * enabled cull distances and can be at most > + * g...

...able (AllocaInst). Later on I intend to indirectly branch to this address by "dereferencing" the variable. Is this possible? I tried creating an instance of AllocaInst but I'm not quite sure which type to use. Using block->getType() results in a segmentation fault (Cannot allocate unsized type %myVar = alloca label). Code might help: AllocaInst *myVar = new AllocaInst(blockToStore.getType(), "myVar", curBlock); new StoreInst(&blockToStore, myVar); I guess I should use an integer type to store the address but then LLVM complains about type mismatch as I don not kno...

Hi folks, We seem to be converging on how the representation of scalable vectors will be implemented in IR, and we also have support for such vectors in the AArch64 back-end. We're also fresh out of the release process and have a good number of months to hash out potential problems until next release. What are the next steps to get this merged into trunk? Given this is a major change to IR,

...t; Tobias Klausmann (10): >> glapi: add GL_ARB_cull_distance >> mesa/main: add support for GL_ARB_cull_distance >> mesa/prog: Add varyings for arb_cull_distance >> mesa/st: add support for GL_ARB_cull_distance >> glsl: Add a helper to see if an array was unsize in the shader >> glsl: Add arb_cull_distance support >> i965: rename UsesClipDistanceOut to UsesClipCullDistanceOut >> gallium: add support for arb_cull_distance >> nouveau/codegen: sort in galliums cull_distance semantic into the >> drivers bitmask &...

Hi all. Recently I was looking for an IMAP-server with Oracle support and unfortunatelly I couldn't find one. It was a surprise for me but there is no such functionality at all. So I've chosen an IMAP-server with most flexible and convinient architecture that was Dovecot-1.2.9 and written a driver for Oracle RDBMS support. I used Oracle Pro*C so a Pro*C preprocessor is needed to

...glapi: add GL_ARB_cull_distance >>>> mesa/main: add support for GL_ARB_cull_distance >>>> mesa/prog: Add varyings for arb_cull_distance >>>> mesa/st: add support for GL_ARB_cull_distance >>>> glsl: Add a helper to see if an array was unsize in the shader >>>> glsl: Add arb_cull_distance support >>>> i965: rename UsesClipDistanceOut to UsesClipCullDistanceOut >>>> gallium: add support for arb_cull_distance >>>> nouveau/codegen: sort in galliums cull_distance semantic into...

...on I intend > to indirectly branch to this address by "dereferencing" the variable. > > Is this possible? I tried creating an instance of AllocaInst but I'm not > quite sure which type to use. Using block->getType() results in a > segmentation fault (Cannot allocate unsized type %myVar = alloca label). > > Code might help: > > AllocaInst *myVar = new AllocaInst(blockToStore.getType(), "myVar", > curBlock); > new StoreInst(&blockToStore, myVar); > > I guess I should use an integer type to store the address but then LLVM > comp...

Hi David, Sorry to bother you, but I would like to get some suggestions on your recent work of token type. I’m currently working on changing gc.statepoint to return a token type instead of a i32 type. The reason is that with the current implementation, gc.statepoint could potentially be fed into PHI nodes, and break RewriteStatepointsForGC pass later. Using token type would help us to avoid

...tructions , I can't keep track on > them. I > > try to convert them to Value and get the type or simply get the type of > > instruction, but have the following error: > > > > Assertion `Ty->isSized() && "Cannot getTypeInfo() on a type that is > > unsized!"' failed. > > You've got two issues you need to take account of here. > > First is that the Type of an instruction is the type of the Value it > produces, which isn't necessarily what you want. Some instructions > ("ret" in your case, but also other b...

...{ > %load = load %struct_ty, %struct_ty* %p > ret %struct_ty %load > } > > $ opt -O2 t.ll -S > lib/IR/DataLayout.cpp:623: unsigned int llvm::DataLayout::getAlignment(llvm::Type *, bool) const: Assertion `Ty->isSized() && "Cannot getTypeInfo() on a type that is unsized!"' failed. Thanks David! I’ve actually hacked to add token type into struct type and ended up with the same failure as above. I will take a look at the catchpad and cleanuppad code, and create a patch to add token landingpad and have you review it. thanks, chen > > As a practic...

...e to the opposite conclusion. While in theory the intrinsics and opaque types are more targeted and confined, this only remains true *if* we don't end up teaching a bunch of transformations and analysis passes about them. However, I feel it is inevitable that we will:  1. While we already have unsized types in the IR, SV will add more of them, and opaque or otherwise, there will be some cost to making all of the relevant places in the optimizer not crash in their presence. This cost we end up paying either way.  2. We're going to end up wanting to optimize SV operations. If we have intrin...

...unsigned integer that represents the size_t type is no longer known. The C spec states in section 6.5.3.4.4 that "The value of the result is implementation-defined, and its type(an unsigned integer type) is size_t, defined in <stddef.h> (and other headers)." SPIR defines size_t as a unsized unsigned integer and as such cannot be known until the SPIR binary is lowered to the device. At that time, SPIR is known and as such can be lowered correctly to its type. *** Hal Finkel: Handling FP_CONTRACT *** *****Comment: The current specification provides a mechanism for handling...

...%struct_ty @f(%struct_ty* %p) { %load = load %struct_ty, %struct_ty* %p ret %struct_ty %load } $ opt -O2 t.ll -S lib/IR/DataLayout.cpp:623: unsigned int llvm::DataLayout::getAlignment(llvm::Type *, bool) const: Assertion `Ty->isSized() && "Cannot getTypeInfo() on a type that is unsized!"' failed. Thanks David! I’ve actually hacked to add token type into struct type and ended up with the same failure as above. I will take a look at the catchpad and cleanuppad code, and create a patch to add token landingpad and have you review it. thanks, chen As a practical matter,...