similar to: [LLVMdev] LLVM 2.7 build failure: no matching function for call to 'llvm::MemoryBuffer::getFile

Hi, I was having a little trouble installing clang.... while llvm installs properly but clang gives this error on invoking make in Clang make[2]: Leaving directory `/home/na2271/Desktop/llvm-2.3-x/tools/clang/lib/Headers' make[2]: Entering directory `/home/na2271/Desktop/llvm-2.3-x/tools/clang/lib/Basic' llvm[2]: Compiling SourceManager.cpp for Release build SourceManager.cpp: In member

On 03/16/2017 06:22 PM, Mehdi Amini via llvm-dev wrote: >> On Mar 16, 2017, at 10:29 AM, Roger Ferrer Ibanez via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi all, >> >> I'm implementing interleaved source in assembly output. Early reviews raised the concern > Is there a patch up for review? https://reviews.llvm.org/D30898

Hi all, I'm implementing interleaved source in assembly output. Early reviews raised the concern that the current implementation will be opening files (using a llvm::MemoryBuffer) that are likely to be in the memory of the front end (commonly clang but I think we want this to be front end agnostic). I'm now exploring ideas to avoid reopening files and let LLVM reuse the files the FE had

\tools\clang\tools\CIndex && D:\Tools\Building\cmake\bin\cmake.exe -E cmake_link_script CMakeFiles\CIndex.dir\link.txt --verbose=1 D:\Tools\Building\gcc\bin\g++.exe -shared -o ..\..\..\..\bin\libCIndex.dll -Wl,--out-implib,..\..\..\..\lib\libCIndex.dll.a -Wl,--major-image-version,0,--minor-image-version,0 CMakeFiles\CIndex.dir\CIndex.cpp.obj ..\..\..\..\lib\libLLVMMC.a

I'm using the latest llvm/clang 2.8 releases and am getting EXC_BAD_ACCESS crashes in ContentCache::getBuffer. This happens when I'm printing out errors from a compilation run and iterating over TextDiagnosticBuffer returned errors. When checking the errors, I construct a FullSourceLoc and do: int LineNum = SourceLoc.getInstantiationLineNumber(); int ColNum =

Thank you all for your feedback, this has been very helpful! There have been a few important points raised by different people. Below I try to address them one by one. I hope that you don't mind me sending it in one email. Please let me know if I missed something! *QUESTIONS RAISED IN PREVIOUS EMAILS* On 02/06/2020 20:51, Eli Friedman wrote: > Separate from clang, LLVM itself actually

Hi guys, In porting our project over to LLVM-2.8 today I ran into a change that should probably go in the 2.8 release notes. After r100485, the MemoryBuffer::getMemBuffer went from: /// getMemBuffer - Open the specified memory range as a MemoryBuffer. Note /// that EndPtr[0] must be a null byte and be accessible!

On Tue, Jun 2, 2020 at 6:38 PM Richard Smith via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Tue, 2 Jun 2020 at 05:08, Andrzej Warzynski via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> *TL;DR* >> >> We propose some non-trivial refactoring in Clang and LLVM to enable >> further work on Flang driver. >> >> *SUMMARY* >> We

On Tue, Dec 6, 2011 at 6:23 AM, Douglas Gregor <dgregor at apple.com> wrote: > > > Sent from my iPhone > > On Dec 5, 2011, at 9:04 PM, Daniel Dunbar <daniel at zuster.org> wrote: > >> Hi Manuel, >> >> On Sun, Dec 4, 2011 at 9:06 AM, Manuel Klimek <klimek at google.com> wrote: >>> On Sat, Dec 3, 2011 at 10:33 PM, Douglas Gregor

MemoryBuffer requires that its buffer be NULL terminated. This is handy for some users, but it is a hard requirement for some cases. For example, currently I get the following valgrind error when doing LTO and fetching an archive member: at 0x6DAC36E: llvm::MemoryBuffer::init(char const*, char const*) (MemoryBuffer.cpp:50) Address 0x5fecea0 is 0 bytes after a block of size 464 alloc'd

On Thu, Sep 24, 2009 at 4:26 PM, Gordon Henriksen <gordonhenriksen at me.com> wrote: > NUL-termination is an optimization, in particular for clang's parser, > where it's cheaper to check for '\0' to signal EOF than it is to > compare pointers. Its presence doesn't move the end iterator (just > makes it dereference-able) and in no way impacts your ability to

On Thu, Sep 24, 2009 at 2:32 PM, Chris Lattner <clattner at apple.com> wrote: > > On Sep 24, 2009, at 1:23 PM, OvermindDL1 wrote: > >> I was writing something using MemoryBuffer, and while looking through >> its code I came across line 59: >> assert(BufEnd[0] == 0 && "Buffer is not null terminated!"); >> I am curious if the MemoryBuffer

On Thu, Sep 24, 2009 at 5:38 PM, Gordon Henriksen <gordonhenriksen at me.com> wrote: > On 2009-09-24, at 18:56, OvermindDL1 wrote: > > Out of curiosity, what code in Clang is optimized by doing a > pointer derefence then compare to 0, rather then just comparing two > points directly? Does not seem that efficient when laid out like that, > which is why I am curious what

Is this for user prompts, or just reading data from stdin? You can use MemoryBuffer::getSTDIN to read the contents of stdin into a memory buffer. Then you can get the data pointer and size and read it in. As far as I know, there is not a good way to implement user prompts with the LLVM APIs. On Mon, Jan 14, 2013 at 4:57 AM, Journeyer J. Joh <oosaprogrammer at gmail.com>wrote: >

On 7 November 2011 22:00, Bill Wendling <wendling at apple.com> wrote: > We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit: > >        http://llvm.org/pre-releases/3.0/rc3/ > > for the sources. There are also binaries for Darwin up there, with > more to come during the week. Please build this release candidate, > test it out

Sent from my iPhone On Dec 5, 2011, at 9:04 PM, Daniel Dunbar <daniel at zuster.org> wrote: > Hi Manuel, > > On Sun, Dec 4, 2011 at 9:06 AM, Manuel Klimek <klimek at google.com> wrote: >> On Sat, Dec 3, 2011 at 10:33 PM, Douglas Gregor <dgregor at apple.com> wrote: >>> Hi Manuel, >>> >>> On Nov 28, 2011, at 2:49 AM, Manuel Klimek

Hi Manuel, On Sun, Dec 4, 2011 at 9:06 AM, Manuel Klimek <klimek at google.com> wrote: > On Sat, Dec 3, 2011 at 10:33 PM, Douglas Gregor <dgregor at apple.com> wrote: >> Hi Manuel, >> >> On Nov 28, 2011, at 2:49 AM, Manuel Klimek wrote: >> >>> Hi, >>> >>> while working on tooling on top of clang/llvm we found the file system

Hello list, I learned that under LLVM, #including of <iostream> is forbidden. Instead LLVM provides llvm::raw_ostream(for std::cout, std::cerr) and llvm::MemoryBuffer(for input stream). And using of llvm::raw_ostream is pretty easy but for me learning of how to use llvm::MemoryBuffer is pretty much difficult. I found a good sample code; utils/yaml2obj/yaml2obj.cpp. The function, main() in

And for this kind of question I think I would better hold in. There would be more important issue worth on this list. For this reason I am sorry. Sincerely Journeyer 2013/1/15 Journeyer J. Joh <oosaprogrammer at gmail.com>: > Hi Justin Holewinski, > >>> As far as I know, there is not a good way to implement user prompts with the LLVM APIs. > > This info helps me a

On Sun, Dec 4, 2011 at 9:06 AM, Manuel Klimek <klimek at google.com> wrote: > On Sat, Dec 3, 2011 at 10:33 PM, Douglas Gregor <dgregor at apple.com> wrote: >> Hi Manuel, >> >> On Nov 28, 2011, at 2:49 AM, Manuel Klimek wrote: >> >>> Hi, >>> >>> while working on tooling on top of clang/llvm we found the file system >>>