search for: frontendobjc

...on of opt, but not the optimized version. Does anyone know what the problem is or have any suggestions for debugging this? My install went fine except for some failures during make check (Unexpected Failures: 92). All failures were in one of the following: LLVM::FrontendC++ LLVM::FrontendC LLVM::FrontendObjC++ LLVM::FrontendObjC LLVM::Transforms Thanks, Scott On Tue, Mar 16, 2010 at 9:24 AM, Ben Ransford <ransford at cs.umass.edu> wrote: > Hello, > > I just built a virgin ToT (r98634) for release on vanilla Snow > Leopard.  It seems that the Hello pass doesn't want to load becau...

On Dec 2, 2010, at 2:37 PM, Scott Ricketts wrote: > My install went fine except for some failures during make check > (Unexpected Failures: 92). All failures were in one of the following: > > LLVM::FrontendC++ > LLVM::FrontendC > LLVM::FrontendObjC++ > LLVM::FrontendObjC These are actually testing llvm-gcc, not llvm. If you build and install llvm-gcc, and tell llvm where it is, they should work. > LLVM::Transforms These should not fail and indicate some kind of problem.

...wrote: > > On Dec 2, 2010, at 2:37 PM, Scott Ricketts wrote: > >> My install went fine except for some failures during make check >> (Unexpected Failures: 92). All failures were in one of the following: >> >> LLVM::FrontendC++ >> LLVM::FrontendC >> LLVM::FrontendObjC++ >> LLVM::FrontendObjC > > These are actually testing llvm-gcc, not llvm.  If you build and install llvm-gcc, and tell llvm where it is, they should work. > >> LLVM::Transforms > > These should not fail and indicate some kind of problem. > >

Hello, I just built a virgin ToT (r98634) for release on vanilla Snow Leopard. It seems that the Hello pass doesn't want to load because of undefined symbols: builddir% ../llvm/configure --prefix=$(PWD)/../installdir --enable-optimized builddir% make builddir% make install && cd ../installdir installdir% bin/opt -load lib/libLLVMHello.dylib Error opening

...LLVM :: FrontendC++/2006-11-06-StackTrace.cpp LLVM :: FrontendC++/2006-11-30-Pubnames.cpp LLVM :: FrontendC++/2010-08-31-ByValArg.cpp LLVM :: FrontendC/2009-02-17-BitField-dbg.c LLVM :: FrontendC/2010-01-14-StaticVariable.c LLVM :: FrontendC/2010-02-16-DbgVarScope.c LLVM :: FrontendObjC/2009-08-17-DebugInfo.m - Devang

...0, at 2:37 PM, Scott Ricketts wrote: >> >>> My install went fine except for some failures during make check >>> (Unexpected Failures: 92). All failures were in one of the following: >>> >>> LLVM::FrontendC++ >>> LLVM::FrontendC >>> LLVM::FrontendObjC++ >>> LLVM::FrontendObjC >> >> These are actually testing llvm-gcc, not llvm. If you build and install llvm-gcc, and tell llvm where it is, they should work. >> >>> LLVM::Transforms >> >> These should not fail and indicate some kind of problem. &g...

On Feb 12, 2011, at 2:07 AM, Nathan Jeffords wrote: > Hello All, > > I have created a set of patches that get dwarf debugging support working for the COFF object file. I also believe I have fixed what appears to be a bug in how line info sections are referred to from the DW_TAG_compile_unit DIE. I have run some basic tests, analyzed dumps of both the objects files and the final

...6-11-06-StackTrace.cpp > LLVM :: FrontendC++/2006-11-30-Pubnames.cpp > LLVM :: FrontendC++/2010-08-31-ByValArg.cpp > LLVM :: FrontendC/2009-02-17-BitField-dbg.c > LLVM :: FrontendC/2010-01-14-StaticVariable.c > LLVM :: FrontendC/2010-02-16-DbgVarScope.c > LLVM :: FrontendObjC/2009-08-17-DebugInfo.m This is because of @@ -1903,7 +1912,8 @@ addLabel(Die, dwarf::DW_AT_stmt_list, dwarf::DW_FORM_addr, Asm->GetTempSymbol("section_line")); else - addUInt(Die, dwarf::DW_AT_stmt_list, dwarf::DW_FORM_data4, 0); + addSectionOffset(Die, d...

Hello All, I have created a set of patches that get dwarf debugging support working for the COFF object file. I also believe I have fixed what appears to be a bug in how line info sections are referred to from the DW_TAG_compile_unit DIE. I have run some basic tests, analyzed dumps of both the objects files and the final executables, and run a test program against mingw-gdb and everything looks

LLVMers, The LLVM 2.1 pre-release version2 is now available: http://llvm.org/prereleases/2.1/version2/ You can help test this pre-release by doing one of the following: 1) Download llvm-2.1, llvm-test-2.1, and the appropriate llvm-gcc4.0 binary. Run "make check" and the full llvm-test suite (make TEST=nightly report). 2) Download llvm-2.1, llvm-test-2.1, and the llvm-gcc4.0 source.

...me/jo/Delta/llvm/test/CodeGen/X86/dg.exp ... Running /home/jo/Delta/llvm/test/DebugInfo/dg.exp ... Running /home/jo/Delta/llvm/test/ExecutionEngine/dg.exp ... Running /home/jo/Delta/llvm/test/Feature/dg.exp ... Running /home/jo/Delta/llvm/test/FrontendAda/dg.exp ... Running /home/jo/Delta/llvm/test/FrontendObjC/dg.exp ... Running /home/jo/Delta/llvm/test/Integer/dg.exp ... Running /home/jo/Delta/llvm/test/Linker/dg.exp ... Running /home/jo/Delta/llvm/test/Other/dg.exp ... Running /home/jo/Delta/llvm/test/TableGen/dg.exp ... Running /home/jo/Delta/llvm/test/Transforms/ADCE/dg.exp ... Running /home/jo/Delta...

On Mon, Feb 23, 2009 at 12:12 AM, Aaron Gray < aaronngray.lists at googlemail.com> wrote: > On Sun, Feb 22, 2009 at 11:15 PM, Anton Korobeynikov < > anton at korobeynikov.info> wrote: > >> >> Actually its [configure-stage3-intl] where its hanging. >> >> This can easily be due to inline FP math in the stdlib headers. For >> example - I had to

...D__STDC_LIMIT_MACROS -g -fno-exceptions -Woverloaded-virtual -pedantic -Wall -W -Wwrite-strings -Wno-long-long -Wunused -Wno-unused-parameter -c NoCompileUnit.o -o NoCompileUnit.exe g++: NoCompileUnit.o: linker input file unused because linking not done Running /home/kooijman/src/llvm-trunk/test/FrontendObjC/dg.exp ... Running /home/kooijman/src/llvm-trunk/test/Integer/dg.exp ... Running /home/kooijman/src/llvm-trunk/test/LLVMC/dg.exp ... Running /home/kooijman/src/llvm-trunk/test/Linker/dg.exp ... Running /home/kooijman/src/llvm-trunk/test/Other/dg.exp ... Running /home/kooijman/src/llvm-trunk/test/Ta...

LLVMers, The 2.1 pre-release (version 1) is available for testing: http://llvm.org/prereleases/2.1/version1/ I'm looking for members of the LLVM community to test the 2.1 release. There are 2 ways you can help: 1) Download llvm-2.1, llvm-test-2.1, and the appropriate llvm-gcc4.0 binary. Run "make check" and the full llvm-test suite (make TEST=nightly report). 2) Download

...ted abnormally Running /home/edwin/llvm-svn/llvm/test/DebugInfo/dg.exp ... Running /home/edwin/llvm-svn/llvm/test/ExecutionEngine/dg.exp ... Running /home/edwin/llvm-svn/llvm/test/Feature/dg.exp ... Running /home/edwin/llvm-svn/llvm/test/FrontendAda/dg.exp ... Running /home/edwin/llvm-svn/llvm/test/FrontendObjC/dg.exp ... Running /home/edwin/llvm-svn/llvm/test/Integer/dg.exp ... Running /home/edwin/llvm-svn/llvm/test/Linker/dg.exp ... Running /home/edwin/llvm-svn/llvm/test/Other/dg.exp ... Running /home/edwin/llvm-svn/llvm/test/TableGen/dg.exp ... Running /home/edwin/llvm-svn/llvm/test/Transforms/ADCE/dg....