search for: mydsp

...ed code, but in a nice and > maintainable > form. > > -Chris > > Thanks, I will need also to compile new fields in the result C++ class, thus i need a way to get an access on the class struct field part. I see something like: std::vector<const Type*>StructTy_struct_mydsp_fields; StructTy_struct_mydsp_fields.push_back(StructTy_struct_dsp); StructType* StructTy_struct_mydsp = StructType::get (StructTy_struct_mydsp_fields, /*isPacked=*/false); mod->addTypeName("struct.mydsp", StructTy_struct_mydsp); in the generated llvm2cpp code, i guess it is...

On 07/04/2013 01:39 PM, Stéphane Letz wrote: > Hi, > > Our DSL can generate C or directly generate LLVM IR. With LLVM 3.3, we can vectorize the C produced code using clang with -O3, or clang with -O1 then opt -O3 -vectorize-loops. But the same program generating LLVM IR version cannot be vectorized with opt -O3 -vectorize-loops. So our guess is that our generated LLVM IR lacks some

Hi, Our DSL can generate C or directly generate LLVM IR. With LLVM 3.3, we can vectorize the C produced code using clang with -O3, or clang with -O1 then opt -O3 -vectorize-loops. But the same program generating LLVM IR version cannot be vectorized with opt -O3 -vectorize-loops. So our guess is that our generated LLVM IR lacks some informations that are needed by the vectorization passes to

Here is patch with manpages for ogg123(1), mp3tovorbis(1) and vorbize(1). Manpages are in pod format, because it is the most readable man source, and are compiled by pod2man. all and clean for man/ work. Install and uninstall for man/ seem to work. Manpages are GPLed of course. <HR NOSHADE> <UL> <LI>text/plain attachment: manpages.diff </UL> -------------- next part