similar to: [LLVMdev] LLVM: bitcode with llvm-gcc (mingw) for windows

Hi, i'm currently building a small JIT compiler. For the language I need a runtime library for some special math functions. I think the best would be to compile the lib to bitcode and link it. The compiler should be integrated in a product and as of this, it must work under windows (VC10, 64bit). So is it possible to build the math lib with the mingw llvm-gcc build an link it later with the

Do you want to be able to debug from your main code, and step into the JITed code? Do you want to be able to set breakpoints, list callstacks, etc in the JITed code? Do you want to, from a crash, identify where in your JITed code it went wrong? The first two are definitely one or more order(s) of magnitude harder to solve than the third one, since you basically have to tell your debugger that

Hi Björn, I'm not sure I understand what you are actually trying to achieve. Do you want to be able to debug from your main code, and step into the JITed code? Do you want to be able to set breakpoints, list callstacks, etc in the JITed code? Do you want to, from a crash, identify where in your JITed code it went wrong? The first two are definitely one or more order(s) of magnitude harder

Hello, llvm-dev. thank you for your interest in my question. Currently, I compiled simple c source code (hello.c) in lunux and windows, and I tried to simple test . first case: hello.bc (compiled with "-emit-llvm" on windows) -> lli.exe(linux). second case: hello.bc (compiled with "-emit-llvm" on linux) -> lli.exe(windows). second case return good result. but First case

2011/10/6 Aaron Ballman <aaron at aaronballman.com> > On Thu, Oct 6, 2011 at 2:00 PM, Ruben Van Boxem > <vanboxem.ruben at gmail.com> wrote: > > When building LLVM/Clang, I get the following build failure: > > > > MinGW-w64 provides the necessary typedefs and declarations. I adjusted > the > > ifdef's to include a check for a the MinGW-w64-specific

Anton-- I had some problems just getting a binary of mingw to run on my Windows box, so perhaps, if you're willing, a step-by-step "download this, install it here, download this other, install it here, download this optional piece if you want X and install it here, now compile hello.cc and look at what you've got" kind of installation guide would be helpful. (I got lost between

On Thu, Oct 6, 2011 at 2:00 PM, Ruben Van Boxem <vanboxem.ruben at gmail.com> wrote: > When building LLVM/Clang, I get the following build failure: > > MinGW-w64 provides the necessary typedefs and declarations. I adjusted the > ifdef's to include a check for a the MinGW-w64-specific symbol of choice to > differentiate mingw.org vs mingw-w64. Tested on i686-w64-mingw32 and

Dear LLVM-DEV Hello I am Dueky. I knew about llvm 3 months ago, and I have studied it.. I read Document for llvm in llvm.org, and I have tried compile to source file about llvm and llvm-gcc. But I could not make a success of compile to the "mingw-llvm-gcc in windows". I saw binary file "mingw-llvm-gcc for windows" , but I couldn't find the "how to compile to the

2011/10/6 Aaron Ballman <aaron at aaronballman.com> > On Thu, Oct 6, 2011 at 2:09 PM, Ruben Van Boxem > <vanboxem.ruben at gmail.com> wrote: > > You're welcome! Please remember that MinGW-w64 does not mean it is > 64-bit. > > It provides both 32- and 64-bit headers/libs. The "w64" in the name was > > originally because that was the

Hello, Dueky > But I could not make a success of compile to the "mingw-llvm-gcc in > windows". > I saw binary file "mingw-llvm-gcc for windows" , but I couldn't find > the "how to compile to the mingw-llvm-gcc in windows". In general, compilation of llvm-gcc for mingw is the same as compilation of llvm-gcc for any other platform. However, there are

I managed to build clang on mingw/msys today. Running configure, make install worked for both debug and optimized builds in general. However there were a few hitches along the way. Make would fail with: ln: creating symbolic link `/d/super/dump/code/llvm/llvm-project/llvm/build.clang/Release+Asserts/bin/clang++.exe' to `clang.exe': No such file or directory ln: creating symbolic link

Hi, Has anyone built llvm-gcc-4.2-2.9 using mingw-w64 on Windows 7 64-bit OS? The binaries available in the download website LLVM-GCC 4.2 Front End Binaries for Mingw32/x86<http://llvm.org/releases/2.9/llvm-gcc4.2-2.9-x86-mingw32.tar.bz2> do not build applications (not surprisingly) for 64-bit Windows 7 (-m64 is disabled). I am both compiling and linking an application (to produce a

Good morning. I don't understand relation between output.log and error.log. It seems all LLVM libraries are not found on linking opt.exe. Please show us logs with command lines with make VERBOSE=1 It would be better only then to touch a few files. (eg. lib/Transforms/Scalar/GVN.cpp) The warning of --export-dynamic might be harmless, and you may add the option --enable-auto-import IIRC

On Thu, Oct 6, 2011 at 2:09 PM, Ruben Van Boxem <vanboxem.ruben at gmail.com> wrote: > You're welcome! Please remember that MinGW-w64 does not mean it is 64-bit. > It provides both 32- and 64-bit headers/libs. The "w64" in the name was > originally because that was the project's principal goal, among extending > the API completeness and compatibility with MSVC.

Anton Korobeynikov wrote: >> Thanks Bob and John for the response. I am having problems building >> poolalloc with my MinGW and gcc 4.4.0 setup. Running make in the poolalloc >> directory results in a bunch of "undefined reference to ..." link errors >> building Release/lib/LLVMDataStructure.dll. I looked at the command line for >> > Hrm... John, is

Hi, I have installed the latest MinGW (version 4.6.3 i386, not version 3.X) and then compiled the LLVM source files (version 2.9) on Windows platform (using the default configuration). It seems that those binary tools (such as llvm-bcanalyzer, opt, etc.) have been successfully generated, as they even work well with existing bitcode files compiled and linked on Linux platform (Ubuntu

> Thanks Bob and John for the response. I am having problems building > poolalloc with my MinGW and gcc 4.4.0 setup. Running make in the poolalloc > directory results in a bunch of "undefined reference to ..." link errors > building Release/lib/LLVMDataStructure.dll. I looked at the command line for Hrm... John, is poolalloc a loadable module? If yes, then it won't work

reverting doesn't help. Here are the logs: http://old.nabble.com/file/p29834726/output.log output.log http://old.nabble.com/file/p29834726/error.log error.log which mingw gcc + binutils versions are known to work (or better, the one that you guys use)? -- View this message in context: http://old.nabble.com/Compiling-LLVM-2.7-with-MinGW-GCC-4.5.0-tp29810752p29834726.html Sent from the LLVM -

On 28 April 2015 at 00:30, Reid Kleckner <rnk at google.com> wrote: > I think Paweł identified the problem. The frames on the stack between the > setjmp and longjmp must have valid unwind information, which is described > here: > https://msdn.microsoft.com/en-us/library/ft9x1kdx.aspx?f=255&MSPPError=-2147217396 > > In particular, it has this line about JITed code: >

Hello there! I'm stuck here on my CentOS6 w/ current EPEL's version of mingw32/64 gcc (4.9.2), jealous about the Ubuntu's 5.3.0 version and even more jealous about Fedora 24's top-recent 6.1.0.. and now I need msvcr120.dll compatibility (provided by gcc 6.1.0). Has anybody any experience w/ recompiling Fedora's 24 mingw RPMs or another way to get the latest gcc