similar to: [LLVMdev] Problems building llvm on AIX

Reid, I'm just curious to know if these errors are on your new year list :) ---------------- make[1]: Entering directory `/C/projects/build/MinGW/llvm-1-1/lib/System' llvm[1]: Compiling DynamicLibrary.cpp for Debug build In file included from c:/projects/src/llvm-1/llvm/lib/System/DynamicLibrary.cpp:25: c:/projects/src/llvm-1/llvm/lib/System/win32/DynamicLibrary.cpp:22: warning:

Not really. I'm pretty much leaving the win32 directory up to Jeff Cohen these days. I don't have a way to replicate the problem. Reid. On Wed, 2004-12-29 at 12:46, Henrik Bach wrote: > Reid, > > I'm just curious to know if these errors are on your new year list :) > ---------------- > make[1]: Entering directory `/C/projects/build/MinGW/llvm-1-1/lib/System' >

I have no way of duplicating mingw problems either, but in this case the fix is obvious and has been committed. Reid Spencer wrote: >Not really. I'm pretty much leaving the win32 directory up to Jeff Cohen >these days. I don't have a way to replicate the problem. > >Reid. > >On Wed, 2004-12-29 at 12:46, Henrik Bach wrote: > > >>Reid, >>

Hi Lang, On Tue, 13 Aug 2019 at 23:26, Lang Hames <lhames at gmail.com> wrote: >> I also get this message: >> JIT session error: Symbols not found: { raise_error } > > > Ahh -- I see the problem. The DynamicLibrarySearchGenerator is using the getAddressOfSymbol method, which (under the hood) is basically issuing an appropriate dlsym lookup, and that does not find

I'm trying to compile llvm (cvs head) on windows (WinXP sp2) using the lastest mingw, but I'm getting the link errors found below. It seems that the tools are not being linked with win32 api lib (libimagehlp.a and libpsapi.a) which defines the missing symbols. The TOOLS_VERBOSE link command is at the end of the mail and does not contain those libraries. The configure line I'm

The first one failed on a diff: ******************** TEST (simple) 'sse.expandfft' FAILED! ******************** Execution Context Diff: /home/rkotler/llvmpb3/build/projects/test-suite/tools/fpcmp: Compared: 1.139094e-07 and 1.159249e-07 abs. diff = 2.015500e-09 rel.diff = 1.738626e-02 Out of tolerance: rel/abs: 1.600000e-02/0.000000e+00 ******************** TEST (simple)

On Wed, May 7, 2014 at 8:28 AM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- > > From: "Anton Korobeynikov" <anton at korobeynikov.info> > > To: "Hal Finkel" <hfinkel at anl.gov> > > Cc: "Alexey Samsonov" <samsonov at google.com>, "LLVM Developers Mailing > List" <llvmdev at

Hi, I am trying to generate LLVM code that calls a "native" function in the parent program (the program hosting the JIT). I think that I have figured out how to do this, but I get the following assertion failure when the LLVM code is executed: ../llvm/lib/Target/PowerPC/PPCJITInfo.cpp:206: failed assertion `ResultPtr >= -(1 << 23) && ResultPtr < (1 << 23)

when I create the report, there are no failures in it. so maybe these are being filtered for known failures. On 12/12/2012 05:03 PM, reed kotler wrote: > The first one failed on a diff: > ******************** TEST (simple) 'sse.expandfft' FAILED! > ******************** > Execution Context Diff: > /home/rkotler/llvmpb3/build/projects/test-suite/tools/fpcmp: Compared: >

I use the 'make TEST=simple' as a pre-commit test. I think that everybody should run these tests before committing to LLVM. On Dec 12, 2012, at 5:06 PM, reed kotler <rkotler at mips.com> wrote: > when I create the report, there are no failures in it. so maybe these are being filtered for known failures. > > On 12/12/2012 05:03 PM, reed kotler wrote: >> The first

On Fri, 2004-12-31 at 05:30, Francisco Puentes wrote: > Hi again, and thanks (Reid) for your fast response: Glad to help. > > Yes, it works!!! Only changing the order of libraries in the Makefile. Great! > > Nowaday I have my software with the capability of compile assembly, bytecode > (from buffer and file) and link them with a set of libraries. It seems to > work

I'm really sorry for the wide e-mail, but I've exhausted the normal channels. I get: llvm[2]: Linking Release executable tblgen (without symbols) llvm[2]: ======= Finished Linking Release Executable tblgen (without symbols) llvm[2]: Compiling fpcmp.cpp for Release build llvm[2]: Linking Release executable fpcmp (without symbols) llvm[2]: ======= Finished Linking Release Executable

I'm trying to compile LLVM with musl libc library. The compilation process fails on the following: x86_64-linux-musl-g++ -DGTEST_HAS_RTTI=0 -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Support -I../lib/Support -Iinclude -I../include -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter

The interpreter still resolves printf using a hack. It does try to use DynamicLibrary to find it, but fails. DynamicLibrary on Windows only searches the main program executable for symbols, lli.exe in this case. As the C/C++ runtime is in a DLL, it won't find printf in lli.exe. It ought to then search the runtime DLL, the name of which depends on how the binaries are built, but it

Hi, I'm using LLVM 1.8 with the GCC4-frontend on a Slackware 10.2 box (GCC 3.3.6). When issuing the following command (line 14 in a script called manual.sh): llvm-ld -O1 *.trans -L${SOME_LIB_DIR} -L${SOME_OTHER_LIB_DIR} -L${LLVM_FRONT}/lib -lSOME_LIB -lSOME_OTHER_LIB -load=${MY_LIB_DIR}/opt1.so -load=${MY_LIB_DIR}/opt2.so -debug-pass=Details -debug -o test ... I get the following

First error: head file related. Strangely, this code has been there a while, which makes me think that the HAVE_ARC4RANDOM is somehow now showing up as set whereas perhaps it didn't used to be. tfiala at tfiala2:~/lldb/svn/lgs/build$ make make[1]: Entering directory `/mnt/ssd/work/svn/lgs/build/lib/Support' llvm[1]: Compiling Process.cpp for Debug+Asserts build In file included from

On Sat, 11 Sep 2004 13:53:11 -0700 Reid Spencer <reid at x10sys.com> wrote: > On Sat, 2004-09-11 at 12:49, Jeff Cohen wrote: > > > > ===================== MultiSource/Applications/sgefa > > > sgefa is a known XFAIL. See the nightly test results over the last > several months. Actually, you should compare your test results with the > 1.3 release test results

Dimitry Andric <dimitry <at> andric.com> writes: > > On 2010-06-15 18:28, Sunay Ismail wrote: > > I read on web that llvm compiles itself with clang, but could not find the > > instruction to achieve that. I try "./configure CC=clang CXX=clang" but get link > > errors. > > Try using CXX=clang++ instead. Always use clang++ for C++ code. :)

greened at obbligato.org (David A. Greene) writes: > Nikola Smiljanic <popizdeh at gmail.com> writes: > >> I'm not sure if this makes a difference but I ran this >> >> make -j 2 -k LLVMCC_OPTION=clang ENABLE_BUILT_CLANG=1 ENABLE_PARALLEL_REPORT=1 TEST=simple report > ../../report.txt 2>&1 > > That does indeed seem to get me further. Thanks!

I've finally managed to extract from Kaleidoscope one particular thing that it seems to me should be working and isn't. Given the global declaration extern "C" void foo() {} within the same program I have RTDyldMemoryManager::getSymbolAddressInProcess("foo") And it's returning null. (LLVM 3.8, Windows 7 x64.) What am I missing? -------------- next part