similar to: [LLVMdev] MemoryBuffer and its requirement for NULL termination

If I remove this code, diff --git a/tools/gold/gold-plugin.cpp b/tools/gold/gold-plugin.cpp index 46a5f46..a8978d5 100644 --- a/tools/gold/gold-plugin.cpp +++ b/tools/gold/gold-plugin.cpp @@ -428,8 +428,6 @@ getMinVisibility(GlobalValue::VisibilityTypes A, return A; if (B == GlobalValue::HiddenVisibility) return B; - if (A == GlobalValue::ProtectedVisibility) - return A;

When I build LLVM 2.6 after configuring it with the --with-binutils-include option so it points to the gold plugin src/include directory, I get the errors below. I used "cvs -z 9 -d :pserver:anoncvs at sourceware.org:/cvs/src co src" to check out the gold-plugin, as is documented on llvm.org. -------------------------- make[2]: Entering directory

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!

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

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

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 >

I would like to use the LLVM-C bindings to provide LLVM access with an OO-design in another language (D), e.g. map from the C API back up to a D API that closely resembles the original C++ API. Since I would like to have D (with its own exception system) to handle the IO, I need a new C API function (unless there is one and I haven't found it): LLVMBool

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

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

Hi Samba developer people, I still have a problem were winbindd panics every time I run it. I'd hoped this might get fixed as newer releases of Samba came out, but I'm now running 3.0.2pre1 and still the same problem. I want to deploy Samba on Solaris, but was unable to successfully get samba to compile with dmalloc support, so I've had to install onto RedHat 8 and use valgrind

Hello, KWD crashes almost regularly when trying to start OpenOffice.org. I've attached two output files from valgrind to this e-mail (as suggested by David Reveman in another mail 11.7): Use something like: valgrind --tool=memcheck kde-window-decorator .... I'm using Trevino's git version of Compiz in up-to-date Kubuntu Feisty system. Compiz version is

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 code actually is helped by that > pattern? Consider parsing an integer: // With NUL

Hi, http://llvm.org/doxygen/classllvm_1_1MemoryBuffer.html shows "the file, and that this character will read as '\0'. " as a "verbatim text" box. This looks ugly and is probably a mistake. The attached patch removes this extra @verbatim ... @endverbatim from comments. -------------- next part -------------- A non-text attachment was scrubbed... Name:

I believe this assert is wrong since it checks memory outside of the buffer. It shouldn't make assumptions on how callers store the array. Yuri