Hi all, I'm currently working on an extension for clang. Apparently, I'm doing sth incorrectly currently. The Verify complains with Wrong type for attribute signext <8 x i32> (<256 x i1>, i16, <2 x double>)* @_Z4testsDv2_d Now, this information is not that useful. Is it possible to emit this "broken" llvm code in order to better understand what went wrong? -- Roland
Already found it my self: clang++ -cc1 test.cpp -S -o - -disable-llvm-verifier -emit-llvm does the trick. -- Roland ----- Original Message -----> From: "Roland Leißa" <leissa at cs.uni-saarland.de> > To: llvmdev at cs.uiuc.edu > Sent: Donnerstag, 3. Mai 2012 16:39:23 > Subject: [LLVMdev] emit broken llvm code > > Hi all, > > I'm currently working on an extension for clang. Apparently, I'm > doing sth incorrectly currently. The Verify complains with > Wrong type for attribute signext > <8 x i32> (<256 x i1>, i16, <2 x double>)* @_Z4testsDv2_d > > Now, this information is not that useful. Is it possible to emit this > "broken" llvm code in order to better understand what went wrong? > > -- > Roland > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Hi Roland,> I'm currently working on an extension for clang. Apparently, I'm doing sth incorrectly currently. The Verify complains with > Wrong type for attribute signext > <8 x i32> (<256 x i1>, i16,<2 x double>)* @_Z4testsDv2_d > > Now, this information is not that useful. Is it possible to emit this "broken" llvm code in order to better understand what went wrong?you can run in the debugger, put a breakpoint on this verifier message, and rummage around in the verifier to work out what the problem is. Ciao, Duncan.