similar to: Sharing MemoryBuffers between front ends and LLVM

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, 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 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 >> abstractions in clang/llvm to be one of the points that could be nicer >> to integrate with. I’m writing this mail to

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

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

On Tue, Dec 6, 2011 at 2:11 AM, Michael Spencer <bigcheesegs at gmail.com> wrote: > 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: >>> >>>>

On Tue, Dec 6, 2011 at 2:27 AM, Manuel Klimek <klimek at google.com> wrote: > On Tue, Dec 6, 2011 at 2:11 AM, Michael Spencer <bigcheesegs at gmail.com> wrote: >> 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 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 >>>

make[4]: Entering directory `/usr/local/src/llvm-2.7/tools/clang/lib/Basic' llvm[4]: Compiling Builtins.cpp for Release build llvm[4]: Compiling ConvertUTF.c for Release build llvm[4]: Compiling Diagnostic.cpp for Release build llvm[4]: Compiling FileManager.cpp for Release build llvm[4]: Compiling IdentifierTable.cpp for Release build llvm[4]: Compiling SourceLocation.cpp for Release build

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 > abstractions in clang/llvm to be one of the points that could be nicer > to integrate with. I’m writing this mail to propose a strawman and get > some feedback on what you guys think the right way forward is (or > whether we should

On Tue, Dec 6, 2011 at 5:36 PM, Daniel Dunbar <daniel at zuster.org> wrote: > On Tue, Dec 6, 2011 at 2:27 AM, Manuel Klimek <klimek at google.com> wrote: >> On Tue, Dec 6, 2011 at 2:11 AM, Michael Spencer <bigcheesegs at gmail.com> wrote: >>> On Sun, Dec 4, 2011 at 9:06 AM, Manuel Klimek <klimek at google.com> wrote: >>>> On Sat, Dec 3, 2011 at

2011/12/6 Daniel Dunbar <daniel at zuster.org> > On Tue, Dec 6, 2011 at 2:27 AM, Manuel Klimek <klimek at google.com> wrote: > > On Tue, Dec 6, 2011 at 2:11 AM, Michael Spencer <bigcheesegs at gmail.com> > wrote: > >> 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,

Hi, while working on tooling on top of clang/llvm we found the file system abstractions in clang/llvm to be one of the points that could be nicer to integrate with. I’m writing this mail to propose a strawman and get some feedback on what you guys think the right way forward is (or whether we should just leave things as they are). First, the FileManager we have in clang has helped us a lot for

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

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

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 lot. I tried to do a thing that is not possible. Thank you very much. Sincerely Journeyer 2013/1/15 Justin Holewinski <justin.holewinski at gmail.com>: > Is this for user prompts, or just reading data from stdin? You can use >

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: >

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 only supports non-binary, non-null embedded files, or if it supports binary as well. I do not see anything inherently not expecting binary files except for that one line, so I am