similar to: [LLVMdev] LLVM build fails using gcc-4.7.0 and -std=c++11 flags

I've fixed this specific error in r164813. Please let me know if there are more behind it. On Thu, Sep 27, 2012 at 2:16 PM, Sid Manning <sidneym at codeaurora.org> wrote: > > I just updated my llvm sources (revision 164794.) and I see the error, > "overriding non-deleted function" when building with gcc 4.7.0 and passing > -std=c++11. > >

> On Slackware 10.2 (GCC 3.3.6), I got an error during a debug build with the > header files using uintptr_t (not recognised as a type). Putting "#include > <stdint.h>" in include/llvm/BasicBlock.h (llvm) and in > "include/llvm/ValueSymbolTable.h" (frontend) resolved this. Ok. This is now fixed on the release branch. Thanks! > Also, I got linking

The first buildbot failure I can readily find was Monday, 26oct2009 around 7PM PDT. The assertion is Assertion failed: ((i >= FTy->getNumParams() || FTy->getParamType(i) == Params[i]->getType()) && "Calling a function with a bad signature!"), function init, file /Volumes/Sandbox/Buildbot/llvm/

Hi all, This patch, though large, simply moves lib/Analysis/DebugInfo.cpp to lib/VMCore/DebugInfo.cpp and include/llvm/Analysis/DebugInfo.h to include/llvm/DebugInfo.h. Why? Because this module has nothing to do with analysis. It simply defines an interface to the debug info MDNodes. In fact, the lib/VMCore/AsmWriter.cpp file performs a layering violation, because it calculates the DWARF tag

Hi, Op 15-mei-07, om 10:23 heeft Tanya M. Lattner het volgende geschreven: 1) Download llvm-gcc4 binary and llvm. Compile and run make check. I did a debug build on OSX 10.4.9 and everything went fine. Results of "make check" (see ppc.log): === Summary === # of expected passes 1630 # of unexpected failures 21 # of expected failures 2

Hello LLVM & Clang hackers! Based on a discussion with Chris, I would like to propose a Great Renaming of Things for the 3.3-era LLVM and Clang codebase. First and foremost, the two most significant changes I would like to make: 1) llvm/lib/VMCore/... -> llvm/lib/IR/... I've discussed potential names for the VMCore (or LLVMCore) library with lots of folks, and the best idea anyone

Is there a way through the Value class to get the identifier for an unnamed temporary? Or alternatively, could someone point me to the code where temporaries are assigned sequential numbers as identifiers so I can better understand this issue? Thanks, Scott

The recent change in the library structure to make libLLVMCore.a instead of LLVMCore.o has caused a little fallout. The problem is LLVM tools that take a --load option to load a module dynamically may now cause those modules to fail to load at runtime. This occurs because the tool with the --load option might not be linking in all of libLLVMCore.a, but only the object modules actually needed by

On May 26, Reid Spencer wrote: > Alexander, > > Yes, a patch like that would be accepted. Fewer dependencies = good :) > > Some notes on doing this: > > (1) Please make sure you use the std c++ iostream libraries for doing > I/O. No native calls (we end up with portability problems). If you need > something that must be ported, please add it to lib/System Sure. What

On Thu, Nov 22, 2012 at 1:53 AM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > 2012/11/22 Chandler Carruth <chandlerc at google.com>: >> Hello LLVM & Clang hackers! >> >> Based on a discussion with Chris, I would like to propose a Great >> Renaming of Things for the 3.3-era LLVM and Clang codebase. >> >> First and foremost, the two most

On Fri, 2005-05-27 at 18:10 -0400, Alexander Friedman wrote: > On May 26, Reid Spencer wrote: > > Alexander, > > > > Yes, a patch like that would be accepted. Fewer dependencies = good :) > > > > Some notes on doing this: > > > > (1) Please make sure you use the std c++ iostream libraries for doing > > I/O. No native calls (we end up with

Le 2 juin 2010 à 12:21, Eli Friedman a écrit : > On Wed, Jun 2, 2010 at 2:59 AM, Stéphane Letz <letz at free.fr> wrote: >> Hi, >> >> We need to generate "Floating point constants" in our code. In http://llvm.org/docs/LangRef.html it is explained that FP has to follow special encoding rules to be handled by LLVM later one (hexadecimal coding...) >>

There are some bugs against it that state the current progress. The problem is that it depends on how the libraries are being used. Even if you get past the linking problems, you will end up with re-registration of passes and options, etc., which causes asserts. So, for now, there aren't many good solutions. Reid. On Thu, 2006-06-22 at 17:21 -0500, John Criswell wrote: > Has anything

While learning to write LLVM passes and following the precise instructions under http://llvm.org/docs/WritingAnLLVMPass.html, <http://llvm.org/docs/WritingAnLLVMPass.html> I got this error when loading the hello pass to run the test program: opt -load ./Release/lib/Hello.so -hello < test/test.bc > /dev/null Error opening './Release/lib/Hello.so': ./Release/lib/Hello.so:

On Oct 27, 2009, at 11:23 AMPDT, Stuart Hastings wrote: > The first buildbot failure I can readily find was Monday, 26oct2009 > around 7PM PDT. The assertion is > > Assertion failed: ((i >= FTy->getNumParams() || FTy->getParamType(i) > == Params[i]->getType()) && "Calling a function with a bad > signature!"), function init, file

On Jun 27, 2012, at 4:08 PM, Bill Wendling <wendling at apple.com> wrote: > Hi all, > > This patch, though large, simply moves lib/Analysis/DebugInfo.cpp to lib/VMCore/DebugInfo.cpp and include/llvm/Analysis/DebugInfo.h to include/llvm/DebugInfo.h. > > Why? Because this module has nothing to do with analysis. It simply defines an interface to the debug info MDNodes. In

On Thu, Jul 2, 2009 at 2:24 PM, Scott Ricketts<sricketts at maxentric.com> wrote: > Is there a way through the Value class to get the identifier for an > unnamed temporary? Or alternatively, could someone point me to the > code where temporaries are assigned sequential numbers as identifiers > so I can better understand this issue? The relevant code is

On Jun 2, 2010, at 3:28 AMPDT, Stéphane Letz wrote: > > Le 2 juin 2010 à 12:21, Eli Friedman a écrit : > >> On Wed, Jun 2, 2010 at 2:59 AM, Stéphane Letz <letz at free.fr> wrote: >>> Hi, >>> >>> We need to generate "Floating point constants" in our code. In http://llvm.org/docs/LangRef.html it is explained that FP has to follow special

On Thu, Jul 2, 2009 at 2:48 PM, Chris Lattner<clattner at apple.com> wrote: > VMCore will auto-unique value names for you. Most passes just create > all instructions with a name like "tmp" and let VMCore unique them. > Is this enough for you? On Thu, Jul 2, 2009 at 2:50 PM, Eli Friedman<eli.friedman at gmail.com> wrote: > The relevant code is

Hi, I'm writing my first hello world Pass with the class name First, but when I tried to load it using opt, I got the following error: /var/soft/llvm-2.2-build/lib/Transforms/Hello$ opt -load ../../../Debug/lib/First.so --help opt: /var/soft/llvm-2.2/lib/VMCore/Pass.cpp:157: void<unnamed>::PassRegistrar::RegisterPass(llvm::PassInfo&): Assertion `Inserted && "Pass