search for: enumname

...=================================================================== --- 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; ++i) { OS << " " << Ints[i].EnumName; OS << ((i != e-1) ? ", " : " "); - OS << std::string(40-Ints[i].EnumName.size(), ' ') - << "// " << Ints[i].Name << "\n"; + if (Ints[i].EnumName.size() < 40) + OS << std::string(40-Ints[i]...

...======================= >> --- 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; ++i) { >> OS << " " << Ints[i].EnumName; >> OS << ((i != e-1) ? ", " : " "); >> - OS << std::string(40-Ints[i].EnumName.size(), ' ') >> - << "// " << Ints[i].Name << "\n"; >> + if (Ints[i].EnumName.size() < 40) >&...

...h the array, emitting one generator for each batch. + for (MapTy::iterator I = UniqueArgInfos.begin(), + E = UniqueArgInfos.end(); I != E; ++I) { + for (unsigned i = 0, e = I->second.size(); i != e; ++i) { + OS << " case Intrinsic::" << Ints[I->second[i]].EnumName << ":\t\t// " + << Ints[I->second[i]].Name << "\n"; + } + + const std::vector<Record*> &ArgTypes = I->first; + OS << " return M->getOrInsertFunction(Intrinsic::getName(ID), "; + for (unsigned j = 0;...

..._FFMPEG @@ -310,10 +305,17 @@ swfdec_enums.c: $(public_headers) Makefile --vprod " { @VALUENAME@, \"@VALUENAME@\", \"@valuenick@\" }," \ --vtail " { 0, NULL, NULL }\n };\n etype = g_ at type@_register_static (g_intern_static_string (\"@EnumName@\"), values);\n }\n return etype;\n}\n" \ $(public_headers) ) > xgen-sec \ - && cp xgen-sec swfdec_enums.c \ + && (cmp -s xgen-sec swfdec_enums.c || cp xgen-sec swfdec_enums.c ) \ && rm -f xgen-sec -swfdec_as_strings.h: swfdec_as_strings.c compute-stri...

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

...h the array, emitting one generator for each batch. + for (MapTy::iterator I = UniqueArgInfos.begin(), + E = UniqueArgInfos.end(); I != E; ++I) { + for (unsigned i = 0, e = I->second.size(); i != e; ++i) { + OS << " case Intrinsic::" << Ints[I->second[i]].EnumName << ":\t\t// " + << Ints[I->second[i]].Name << "\n"; + } + + const std::vector<Record*> &ArgTypes = I->first; + OS << " return M->getOrInsertFunction(Intrinsic::getName(id), "; + for (unsigned j = 0;...

The following series of patches fill in most of the gaps in the OCaml bindings to libxl, to make them useful for clients such as xapi/xenopsd (from XCP). There are a number of bugfixes to the existing bindings as well. I have an experimental version of xenopsd that successfully uses the new bindings. An earlier version of the first half of the series was submitted to the last by Ian Campbell on

This is v3 of my disk series. What were previously patches 01-06 have been applied. These are the tested and updated remainder, addressing the previous comments. 1 Preparatory work. 2-4 The new parser and its documentation. 5-6 Replace old parsers with calls to the new one. 7-8 Two features, one of them essential. 9 Basic test suite for disk string parsing, as adhoc script.