search for: ostringstream

...const llvm::TargetMachineRegistry::entry* _arch = llvm::TargetMachineRegistry::getClosestTargetForJIT(Err); std::string FeaturesStr; llvm::TargetMachine* target(_arch->CtorFn(*_module, FeaturesStr)); assert(target && "Could not allocate target machine!"); std::ostringstream os; target->addPassesToEmitFile(*_passManager, os, llvm::TargetMachine::AssemblyFile, true); target->addPassesToEmitFileFinish(*_passManager, 0, true); However, in newer versions of llvm, like 2.5 that I'm testing now, I had to change the code to something like this: std...

...bed the logical equivalent of puts/printf/etc. calls inline with code. I am having some difficulties getting the transformation code right. As I understand it, I should be creating a ConstantArray based on the string (in this case I'm taking an instruction, 'disassembling' it to an ostringstream then turning it into a constant array): std::ostringstream instr; (*wp)->print(instr); Constant *itext = ConstantArray::get(instr.str()); This bit seems OK. I am calling a function in my run time system with the signature void mcp_trace_instruction(const char *) by first declaring i...

...stry::entry* _arch = > llvm::TargetMachineRegistry::getClosestTargetForJIT(Err); > >    std::string FeaturesStr; >    llvm::TargetMachine* target(_arch->CtorFn(*_module, FeaturesStr)); >    assert(target && "Could not allocate target machine!"); > >    std::ostringstream os; > >    target->addPassesToEmitFile(*_passManager, os, > llvm::TargetMachine::AssemblyFile, true); >    target->addPassesToEmitFileFinish(*_passManager, 0, true); > > > > However, in newer versions of llvm, like 2.5 that I'm testing now, I > had to change the...

...> llvm::TargetMachineRegistry::getClosestTargetForJIT(Err); > > >    std::string FeaturesStr; > >    llvm::TargetMachine* target(_arch->CtorFn(*_module, FeaturesStr)); > >    assert(target && "Could not allocate target machine!"); > > >    std::ostringstream os; > > >    target->addPassesToEmitFile(*_passManager, os, > > llvm::TargetMachine::AssemblyFile, true); > >    target->addPassesToEmitFileFinish(*_passManager, 0, true); > > > However, in newer versions of llvm, like 2.5 that I'm testing now, I > > ha...

...;-L/local/mnt/workspace/ashoknn/519_libcxx_transition/llvm/build/../../libcxx.artifacts/linux-clang/lib' > /local/mnt/workspace/ashoknn/519_libcxx_transition/llvm/src/tools/bugpoint/ToolRunner.cpp:131:12: error: invalid operands to binary expression ('llvm::raw_ostream' and 'std::ostringstream' > (aka 'basic_ostringstream<char>')) > errs() << OS; > ~~~~~~ ^ ~~ If I remove the -std=c++0x, then the compilation is successful. I checked to see if libc++ itself was compiled with the flag and indeed it was. Any pointers? TIA, Ashok

...older redhat and new ubuntu and with both g++4.1 and g++3.4. I have a problem with character data that is passed back from C++ code. A small example is the following C++ code and R functions. #include <sstream> extern "C" { void extracttxt( char **txt, int *nchars) { std::ostringstream oss; oss << "abcdefghij"; const char *ltxt=oss.str().c_str(); for (int j=0;j<*nchars;j++) *txt[j]=static_cast<char>(ltxt[j]); } } # begin R code dyn.load("test.so") "testtxt" <- function() { nchars <- 80 txt <-...

...Base *c = new Child(); Base *i = new ChildWithInfo(); try { if (Info *inf = llvm::dyn_cast<Info>(c)) { throw std::string("Casted a child to an info incorrectly"); } if (Info *inf = llvm::dyn_cast<Info>(i)) { if (inf->size != 10) { std::ostringstream str; str << "Object was sliced: expected 10 but got " << inf->size; throw str.str(); } } else { throw std::string("Couldn't cast child with info to info"); } } catch (std::string &msg) { std::cout << msg <...

On 2012-06-26 04:22, Ashok Nalkund wrote: ... >> /local/mnt/workspace/ashoknn/519_libcxx_transition/llvm/src/tools/bugpoint/ToolRunner.cpp:131:12: error: invalid operands to binary expression ('llvm::raw_ostream' and 'std::ostringstream' >> (aka 'basic_ostringstream<char>')) >> errs() << OS; >> ~~~~~~ ^ ~~ > Hi Ashok, please try applying this diff from r155978 to your 3.1 release tree: --- llvm/trunk/tools/bugpoint/ToolRunner.cpp 2012/05/02 05:31:31 155977 +++ llvm/tru...

...t; #include <set> using namespace llvm; @@ -469,7 +470,9 @@ } else { if (BugpointIsInterrupted) goto ExitLoops; - std::cout << "Checking instruction '" << I->getName() << "': "; + std::ostringstream SS; I->print(SS); + + std::cout << "Checking instruction '" << SS.str() << "': "; Module *M = BD.deleteInstructionFromProgram(I, Simplification); // Find out if the pass still crashes on this pass... -----...

...assert(target.get() && "Could not allocate target machine!"); llvm::TargetMachine &Target = *target.get(); llvm::FunctionPassManager Passes(new llvm::ExistingModuleProvider(_module)); Passes.add(new llvm::TargetData(*Target.getTargetData())); std::ostringstream os; Target.addPassesToEmitFile(Passes,os,llvm::TargetMachine::AssemblyFile, true); Passes.doInitialization(); for (llvm::Module::iterator I = _module->begin(), E=_module->end(); I != E; ++I) if (!I->isDeclaration()) { Passes.run(*I); }...

"Chris Lattner" <sabre at nondot.org> wrote in message news:Pine.LNX.4.44.0410051204480.5863-100000 at nondot.org... > On Tue, 5 Oct 2004, Alex Vinokur wrote: > > > I would like to use LLVM-GCC to compare its performance with other compilers. > > Something like testsuite "Computing very large Fibonacci numbers" at > >

Dear Maxime, Nyx wrote: > Hello, > > I would like to know how to go about printing the x86 assembly output for a > compiled function (I'm using the JIT). I saw there is a X86IntelAsmPrinter > on doxygen. However, it takes several arguments I don't know how to fill in. > Is there a helper function to create such a pass? Once I have the pass > created, do I just add it

...On 6/26/2012 1:30 AM, Dimitry Andric wrote: > On 2012-06-26 04:22, Ashok Nalkund wrote: > ... >>> /local/mnt/workspace/ashoknn/519_libcxx_transition/llvm/src/tools/bugpoint/ToolRunner.cpp:131:12: error: invalid operands to binary expression ('llvm::raw_ostream' and 'std::ostringstream' >>> (aka 'basic_ostringstream<char>')) >>> errs() << OS; >>> ~~~~~~ ^ ~~ >> > > Hi Ashok, please try applying this diff from r155978 to your 3.1 release tree: > > --- llvm/trunk/tools/bugpoint/ToolRunner.cpp 201...

...eam headers are ok. Also, for bugpoint, we don't really care... we care in the libraries primarily. > @@ -469,7 +470,9 @@ > - std::cout << "Checking instruction '" << I->getName() > << "': "; > + std::ostringstream SS; I->print(SS); > + > + std::cout << "Checking instruction '" << SS.str() << > "': "; Instead of using sstream, why not just use "... << *I << "? -Chris

Hello, I would like to know how to go about printing the x86 assembly output for a compiled function (I'm using the JIT). I saw there is a X86IntelAsmPrinter on doxygen. However, it takes several arguments I don't know how to fill in. Is there a helper function to create such a pass? Once I have the pass created, do I just add it to a FunctionPassManager? Thank you for your time, -

...rged. > 13. You use "std::ostream" a lot. Would it be appropriate to use > "raw_ostream" instead? To make sure that the table definition file looks pretty, I use <iomanip>, and none of those functions work with raw_ostreams. I actually only create three std::ostringstreams – during table generation – so for now I'm going to leave that the way it is. > 14. In DisassemblerTables::setTableFields, you emit things to > "std::cerr". Use "errs()" instead. Or, better yet, > "llvm_report_error". :-) Fixed to use errs(). &gt...

...ConfModules(treeMap,bootstraps,significantVec,mergers,confnew); SEXP name = VECTOR_ELT(gdiag,0); SEXP links = VECTOR_ELT(gdiag,2); Rprintf("teve"); int totalDegree = INTEGER(VECTOR_ELT(gdiag,4))[0]*2; string networkName = string(CHAR(STRING_ELT(name,0))); ofstream outfile; ostringstream oss; int nLinks = INTEGER(links)[0]; oss.str(""); oss << networkName << ".smap"; outfile.open(oss.str().c_str()); outfile << "# modules: " << l << endl; outfile << "# modulelinks: " << "na" <...

...ConfModules(treeMap,bootstraps,significantVec,mergers,confnew); SEXP name = VECTOR_ELT(gdiag,0); SEXP links = VECTOR_ELT(gdiag,2); Rprintf("teve"); int totalDegree = INTEGER(VECTOR_ELT(gdiag,4))[0]*2; string networkName = string(CHAR(STRING_ELT(name,0))); ofstream outfile; ostringstream oss; int nLinks = INTEGER(links)[0]; oss.str(""); oss << networkName << ".smap"; outfile.open(oss.str().c_str()); outfile << "# modules: " << l << endl; outfile << "# modulelinks: " << "na" <...

Hi , I am using LLVM for my Post Graduate course project on Optimization. I am trying to do some insrtumentation to the bytecode.I 've been going through your Instrumentation code for the past few days in /llvm/lib/Transforms/Instrumentation folder and finally found two ways of instrumentation : 1) injecting LLVM bytecode instructions 2) calling an external C function. I am trying both and

..."std::ostream" a lot. Would it be appropriate to use >> "raw_ostream" instead? > > To make sure that the table definition file looks pretty, I use > <iomanip>, and none of those functions work with raw_ostreams. I > actually only create three std::ostringstreams – during table > generation – so for now I'm going to leave that the way it is. I actually find iomanip to be pretty ugly for simple things. llvm/ Support/Format.h lets you do things like: OS << "mynumber: " << format("%4.5f", 1234.412) << '\n...