search for: mainmanmauricio

Hi, I recently updated to current llvm svn and fixed-up the minor compiler errors I encountered. However, at run-time even my Hello world programs crash with a segmentation fault. A concrete program that crashes on my Linux x86_64 Fedora box is: declare void @__ot_runtime_print_int(i8*, i32) define void @main() { entry: call void @__ot_runtime_print_int(i8* null, i32 12) br label %return

...ry low. x86_64 can't encode a full 64-bit immediate offset in the call instruction, so depending on how you are generating this code either you or some code you depend on needs to be jumping through some extra hoops to make this work. Reid On Sun, Jul 31, 2011 at 8:42 AM, Maurice Gittens <mainmanmauricio at gmail.com> wrote: > Hi, > > I recently updated to current llvm svn and fixed-up the minor compiler > errors I encountered. > However, at run-time even my Hello world programs crash with a > segmentation fault. > > A concrete program that crashes on my Linux x86_64 Fedo...

Hi all, maybe it is just me but I feel the function named: llvm::llvm_start_multithreaded(); has to one to many llvm substrings in it. How about renaming it to: llvm::start_multithreaded(); This would be consistent with functions like: llvm::InitializeNativeTarget(); No? Kind regards, Maurice PS: Now I am off to figure out why I suddenly get all these linker

Hi, I need to add a missing include to get current SVN to compile. --- CodeGen/BinaryObject.h (revision 74762) +++ CodeGen/BinaryObject.h (working copy) @@ -18,6 +18,9 @@ #include <string> #include <vector> +#include <stdint.h> + + namespace llvm { My system does not know about uint8_t without this include file. Kind regards, Maurice -------------- next part

Hi, I am using current SVN and in the last week or so, something causing the following assertion failure has changed. void llvm::PATypeHolder::addRef(): Assertion `Ty && "Type Holder has a null type!"' failed. The corresponding stack trace is: #0 0x000000339ec332f5 in raise () from /lib64/libc.so.6 #1 0x000000339ec34b20 in abort () from /lib64/libc.so.6 #2

On Mon, Feb 15, 2010 at 9:30 AM, Holger Schurig <holgerschurig at gmail.com>wrote: > > Clang C++ only gets one big coming-out party (ever); a little > > more time will make a big difference. > > Hmm, wouldn't that speak against jamming this into 2.7 ? Let 2.7 > go out and don't bark at it's C++ status. That gives you a full > release-cycle to get C++

Hi, On Fri, Jul 24, 2009 at 7:03 PM, Chris Lattner <clattner at apple.com> wrote: > > On Jul 24, 2009, at 9:30 AM, Duncan Sands wrote: > > >> The ones that don't can be static functions on the type class that > >> take a context. For example, Type::Int32Ty needs to become a > >> function > >> that takes a context at some point. > >

Hi all, I just svn-updated the 2.5 branch on my machine and I noticed this warning during the build. *** Warning: Linking the shared library /home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool *** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o /home/maurice/installation/llvm/Debug/lib/LLVMMSIL.o /home/maurice/installation/llvm/Debug/lib/LLVMCBackend.o

Hi all, On my Fedora 10 x86-64 the current svn dies in the following way: /home/maurice/installation/llvm-dev/utils/TableGen/Debug/TGLexer.o: In function `llvm::TGLexer::getNextChar()': /home/maurice/installation/llvm-dev/utils/TableGen/TGLexer.cpp:71: undefined reference to `llvm::TGSourceMgr::FindBufferContainingLoc(llvm::TGLoc) const'