search for: intrinsicemitter

...I mean in order to call getOrInsertFunction to get declarations for them. So I wrote this patch, which allows all this code to be generated automatically. Is this a good approach? Dan -- Dan Gohman, Cray Inc. <djg at cray.com> -------------- next part -------------- Index: utils/TableGen/IntrinsicEmitter.cpp =================================================================== RCS file: /var/cvs/llvm/llvm/utils/TableGen/IntrinsicEmitter.cpp,v retrieving revision 1.22 diff -u -r1.22 IntrinsicEmitter.cpp --- utils/TableGen/IntrinsicEmitter.cpp +++ utils/TableGen/IntrinsicEmitter.cpp @@ -38,6 +38,9 @@...

In IntrinsicEmitter::EmitTypeGenerate, called from IntrinsicEmitter::EmitGenerator, here for (unsigned j = 0; j != N; ++j) { OS << " ArgTys.push_back("; EmitTypeGenerate(OS, ParamTys[j], ArgNo); OS << ");\n"; } I'm hitting this assertion: if (ArgType->isS...

On Mon, 5 Feb 2007, Dan Gohman wrote: > LLVM knows what all the types of the intrinsic functions are; I thought, > why are users (including llvm-gcc...) required to duplicate all this > information in order to use them? I mean in order to call > getOrInsertFunction to get declarations for them. That is an excellent question! :) In the bad old days, we used to allow intrinsics

That's a bug. I'm working on a fix.... On Apr 15, 2009, at 10:16 AM, Villmow, Micah wrote: > In IntrinsicEmitter::EmitTypeGenerate, called from > IntrinsicEmitter::EmitGenerator, here > for (unsigned j = 0; j != N; ++j) { > OS << " ArgTys.push_back("; > EmitTypeGenerate(OS, ParamTys[j], ArgNo); > OS << ");\n"; > } > I'm hitting this...

...e GET_INTRINSIC_GENERATOR +#include "llvm/Intrinsics.gen" +#undef GET_INTRINSIC_GENERATOR +} + Value *IntrinsicInst::StripPointerCasts(Value *Ptr) { if (ConstantExpr *CE = dyn_cast<ConstantExpr>(Ptr)) { if (CE->getOpcode() == Instruction::BitCast) { Index: utils/TableGen/IntrinsicEmitter.cpp =================================================================== RCS file: /var/cvs/llvm/llvm/utils/TableGen/IntrinsicEmitter.cpp,v retrieving revision 1.22 diff -u -r1.22 IntrinsicEmitter.cpp --- utils/TableGen/IntrinsicEmitter.cpp +++ utils/TableGen/IntrinsicEmitter.cpp @@ -38,6 +38,9 @@...

...5969927efcd at reviews.llvm.org To: justin.holewinski at gmail.com CC: llvm-commits at cs.uiuc.edu Closed by commit rL213253 (authored by @jholewinski). REPOSITORY rL LLVM http://reviews.llvm.org/D4537 Files: llvm/trunk/test/TableGen/intrinsic-long-name.td llvm/trunk/utils/TableGen/IntrinsicEmitter.cpp Index: llvm/trunk/utils/TableGen/IntrinsicEmitter.cpp =================================================================== --- llvm/trunk/utils/TableGen/IntrinsicEmitter.cpp +++ llvm/trunk/utils/TableGen/IntrinsicEmitter.cpp @@ -129,8 +129,9 @@ for (unsigned i = 0, e = Ints.size(); i != e;...

...gt;> >> >> Closed by commit rL213253 (authored by @jholewinski). >> >> REPOSITORY >> rL LLVM >> >> http://reviews.llvm.org/D4537 >> >> Files: >> llvm/trunk/test/TableGen/intrinsic-long-name.td >> llvm/trunk/utils/TableGen/IntrinsicEmitter.cpp >> >> Index: llvm/trunk/utils/TableGen/IntrinsicEmitter.cpp >> =================================================================== >> --- llvm/trunk/utils/TableGen/IntrinsicEmitter.cpp >> +++ llvm/trunk/utils/TableGen/IntrinsicEmitter.cpp >> @@ -129,8 +129,9...

...ast : Intrinsic<[llvm_float_ty], [llvm_anyfloat_ty, LLVMMatchType<0>]>; Can someone explain what LLVMMatchType does and how to specify it to match the first argument and not the return value? I've tried LLVMMatchType<1> but it fails in IntrinsicEmitter.cpp Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090415/836e3ac9/attachment.html>

Hi, The actual tableGen generate a chain of if/then/else for the intrinsic which is too long for VS 2005, and result in a compile error. I did a small change in table gen so that the if aren't chained so that I could compile (patch attached). This double the algorithmic complexity of the function but it seems that this wasn't a problem. If speed is needed here, we could hash the string

Hello, Cedric > seems that this wasn't a problem. If speed is needed here, we could hash the > string first in a few bin and do the if/then/else in each bin or use a > perfect hash or some hash container. Thanks for the patch. However I have some better solution in the mind, and it will land "really soon" (tm). We can do the the things much better, if we will emit some sort

Hi, The actual tableGen generate a chain of if/then/else for the intrinsic which is too long for VS 2005, and result in a compile error. I did a small change in table gen so that the if aren't chained so that I could compile (patch attached). This double the algorithmic complexity of the function but it seems that this wasn't a problem. If speed is needed here, we could hash the string

Chris, > Anton, your patch definitely sounds like the right way to go, but > should we apply this patch until its ready? If I won't finish my bits today, I'll surely apply Cedric's patch. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

...he back end related to lanemask - now I have 1024-bit long lanemask. But now I get the following error when giving make llc: <<error:unhandled vector type width in intrinsic!>> This error comes from this file https://github.com/llvm-mirror/llvm/blob/master/utils/TableGen/IntrinsicEmitter.cpp, comes from the fact there is no IIT_V128 (nor IIT_V256), and they is a switch case using them in method static void EncodeFixedType(Record *R, std::vector<unsigned char> &ArgCodes, std::vector<unsigned char> &Sig). Is there any reason these enum IIT_Info ( IIT_V128, II...

...[llvm_float_ty], > [llvm_anyfloat_ty, LLVMMatchType<0>]>; > > > Can someone explain what LLVMMatchType does and how to specify it > to match the first argument and not the return value? > > I’ve tried LLVMMatchType<1> but it fails in IntrinsicEmitter.cpp Can you give some more info about how LLVMMatchType<1> fails? That should do what you want.

...r case, the first argument is the first overloaded type, so you should use LLVMMatchType<0> to refer to it. On Apr 15, 2009, at 10:31 AM, Bob Wilson wrote: > That's a bug. I'm working on a fix.... > > On Apr 15, 2009, at 10:16 AM, Villmow, Micah wrote: > >> In IntrinsicEmitter::EmitTypeGenerate, called from >> IntrinsicEmitter::EmitGenerator, here >> for (unsigned j = 0; j != N; ++j) { >> OS << " ArgTys.push_back("; >> EmitTypeGenerate(OS, ParamTys[j], ArgNo); >> OS << ");\n"; >> } >&...

...wing method let SubRegIndices = [sub_32768bit, sub_32768bit_hi], CoveredBySubRegs = 1 in but i am getting following error.. error:Ran out of lanemask bits to represent subregister sub_32768bit_hi_then_sub_16384bit_hi_then_sub_32bit now how to increase lanemask bits? what changes are required in IntrinsicEmitter.cpp file?? Please reply. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170714/ca27668c/attachment.html>

...se >> values are basically already defined in ValueTypes.td) ? >> >> >> So, I managed to get the code compiled. I had issues because I did >> not synchronize the >> following code: >> - enum IIT_Info defined in files >> llvm/utils/TableGen/IntrinsicEmitter.cpp and >> llvm/lib/IR/Function.cpp; >> - enum SympleValueType defined in files >> llvm/include/llvm/CodeGen/ValueTypes.td and >> llvm/include/llvm/CodeGen/MachineValueType.h . >> I was getting errors because of this out-of-sync like: >> - "...

...I still need to define them again (since these > values are basically already defined in ValueTypes.td) ? > > > So, I managed to get the code compiled. I had issues because I did not synchronize the > following code: > - enum IIT_Info defined in files llvm/utils/TableGen/IntrinsicEmitter.cpp and > llvm/lib/IR/Function.cpp; > - enum SympleValueType defined in files llvm/include/llvm/CodeGen/ValueTypes.td and > llvm/include/llvm/CodeGen/MachineValueType.h . > I was getting errors because of this out-of-sync like: > - "error:unhandled vector type wi...

...8bit, sub_32768bit_hi], CoveredBySubRegs = 1 > in > > but i am getting following error.. > > error:Ran out of lanemask bits to represent subregister > sub_32768bit_hi_then_sub_16384bit_hi_then_sub_32bit > > now how to increase lanemask bits? what changes are required > in IntrinsicEmitter.cpp file?? > > Please reply. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170714/f7d70f7a/attachment.html>

...m updating the Fedora packaging of LLVM, and with the 02/20 prerelease it fails to build on ppc64: http://koji.fedoraproject.org/koji/taskinfo?taskID=1148023 make[1]: Entering directory `/builddir/build/BUILD/llvm-2.5/lib/VMCore' llvm[1]: Building Intrinsics.gen.tmp from Intrinsics.td tblgen: IntrinsicEmitter.cpp:137: void EmitTypeForValueType(std::ostream&, llvm::MVT::SimpleValueType): Assertion `false && "Unsupported ValueType!"' failed. make[1]: Leaving directory `/builddir/build/BUILD/llvm-2.5/lib/VMCore' make[1]: *** [/builddir/build/BUILD/llvm-2.5/lib/VMCore/Release/I...