search for: getnewmembuffer

...8 +41,10 @@ void dummy_function() { new llvm::ExistingModuleProvider(0); llvm::createVerifierPass(); - llvm::WriteBitcodeToFile(0, llvm::cout); + llvm::CreateBitcodeWriterPass(*llvm::cout); + llvm::WriteBitcodeToFile(0, *llvm::cout); llvm::ParseBitcodeFile(NULL); + llvm::MemoryBuffer::getNewMemBuffer(0); llvm::createInstructionCombiningPass(); llvm::createScalarReplAggregatesPass();

Thanks. It worked for a few more compilation lines. I now get the following linker error: undefined reference to llvm::MemoryBuffer::getNewMemBuffer(unsigned long, llvm::StringRef) I am surprised since the linker compile line already links with a whole bunch of llvm libraries ... Thanks for your help Romain On Thu, Aug 12, 2010 at 4:03 PM, Rajika Kumarasiri <rajika at wso2.com> wrote: > > > On Thu, Aug 12, 2010 at 6:56 PM, R...

...oblem indicated in README.LLVM does not help .. Thanks Romain On Thu, Aug 12, 2010 at 6:43 PM, Romain Pechayre <rpechayr at gmail.com> wrote: > Thanks. It worked for a few more compilation lines. > I now get the following linker error: > undefined reference to llvm::MemoryBuffer::getNewMemBuffer(unsigned long, > llvm::StringRef) > > I am surprised since the linker compile line already links with a whole > bunch of llvm libraries ... > > Thanks for your help > Romain > > > > On Thu, Aug 12, 2010 at 4:03 PM, Rajika Kumarasiri <rajika at wso2.com>wrote:...

On Thu, Aug 12, 2010 at 6:56 PM, Romain Pechayre <rpechayr at gmail.com> wrote: > Ok. Thank you for your input. New questions :) : > - Is the dev package basically the source code of gcc 4.2 ? Isn't it > already fully included in llvm-gcc code base ? > AFAIR, you need to have the set of headers, gcc-dev.( Some one else may provide you with this information) > - How

...() { > new llvm::ExistingModuleProvider(0); > llvm::createVerifierPass(); > - llvm::WriteBitcodeToFile(0, llvm::cout); > + llvm::CreateBitcodeWriterPass(*llvm::cout); > + llvm::WriteBitcodeToFile(0, *llvm::cout); > llvm::ParseBitcodeFile(NULL); > + llvm::MemoryBuffer::getNewMemBuffer(0); > > llvm::createInstructionCombiningPass(); > llvm::createScalarReplAggregatesPass(); > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/ll...

...ut); llvm::ParseBitcodeFile(NULL); ... and in llvm-gcc-4.2: void dummy_function() { new llvm::ExistingModuleProvider(0); llvm::createVerifierPass(); llvm::CreateBitcodeWriterPass(*llvm::cout); llvm::WriteBitcodeToFile(0, *llvm::cout); llvm::ParseBitcodeFile(NULL); llvm::MemoryBuffer::getNewMemBuffer(0); If the llvm-gcc-4.2 version is correct, the mirror needs to be corrected. Not sure how to do that... Ciao, Duncan.

On Jul 13, 2007, at 9:28 AM, Duncan Sands wrote: > Hi Chris, > >> This is probably a patch that got checked into llvm-gcc4 after devang >> started work on 4.2. Please feel free to update 4.2 to the version >> in >> 4.0. > > no, it doesn't exist in 4.0. hmm. that can not be true. It was applied by Evan on May 07, 2007 to unbreak Apple style builds. -

Hi All, llvm-gcc-4-2 development branch is now open for development at llvm.org/svn/llvm-project/llvm-gcc-4-2 It is not yet ready, it can not even bootstrap. I welcome LLVM developers to test and apply fixes! However, first take a note of ground rules : 1) LLVM developers, use your write access as judiciously as you use it for LLVM development and follow same check-in procedure. 2)

Here is the bulk of the sanitizing. My residual doubts center around the question whether we still do/want to support (un)compressed *byte*code in 2.0/2.1. I need a definitive word on this to proceed. My understanding is that bytecode is already gone, but there are still some functions/enums that really deal with *byte*code (instead of *bit*code). I did not touch those areas, so the attached