similar to: [LLVMdev] Undefined references when LLVM is configured with "--host=x86_64-gnu-linux --target=x86_64-w64-mingw32"

Hi Ruben, Try adding a --build=x86_64-gnu-linux option to configure as well. I don't have that configuration locally, so I can't check to be certain, but IIRC, our configure wants all three for a cross compile like this. -Jim On Aug 21, 2011, at 7:19 AM, Ruben Van Boxem wrote: > Hi, > > I'm getting a returning build failure when building a linux->windows >

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

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

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.

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

When building LLVM/Clang, I get the following build failure: [ 4%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Signals.cpp.obj In file included from M:\Development\Source\LLVM\lib\Support\Signals.cpp:33: M:\Development\Source\LLVM\lib\Support/Windows/Signals.inc:48:17: error: redefinition of '_IMAGEHLP_LINE64' typedef struct _IMAGEHLP_LINE64 { ^

Ruben, Your failure must be due to --disable-pthreads. lib/Support/Unix/Mutex.inc does not have "acquire()". (Shall we fix it?) It might be a bug, though, --disable-pthreads would not make sense to your configuration. --enable-pthreads affects host platform. Note, LLVM and Clang have multi-target architecture. --target is understood as "default target". (EE/JIT should take

I don't know since when, but this file has been changed to remove all the trickery (aka defines) needed for MinGW-w64 (and probably everything else that as forgotten) to succesfully compile it. Attached is a patch that reintroduces the compiler checking. I would like to see this in LLVM 3.0, otherwise (by the looks of the reintroduced code) anything newer than _MSC_VER_1500 will be broken.

Hi Ruben, > I don't know since when, but this file has been changed to remove all the > trickery (aka defines) needed for MinGW-w64 (and probably everything else > that as forgotten) to succesfully compile it. Will you please check which commit introduces the breakage? Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State

Hi Ruben, > It seems this problem is still present on LLVM trunk (and thus 3.0-rc1). > This prevents building a 64-bit Windows LLVM with MinGW-w64. Looks ok, please apply! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hello, NAKAMURA Takumi As you said, I check out the head from svn trunk. I build the source code as the following steps: $./configure --enable-shared $ make After 1 hour, the building procedure is stopped and appear the following error message: c:/strawberry/c/bin/../lib/gcc/i686-w64-mingw32/4.4.3/../../../../i686-w64-mingw 32/bin/ld.exe:

On Mon, Jun 18, 2012 at 12:25 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi all, > >     3. The document now covers 32-bit and 64-bit builds with MinGW tools (if > anybody know of an alternate BINARY distribution of MinGW64 than Drangon's > release, please let me know so I can include it in the document). As was once explained to me by Ruben Van Boxem, what you

Si, ese es el problema, lo que implica por ejemplo que no pueda ordenar el data.frame por grados. Javier Rubén Marcuzzi De: JCMld Enviado: miércoles, 1 de junio de 2016 4:28 Para: 'Javier Marcuzzi'; R-help-es en r-project.org Asunto: RE: [R-es] data.frame colname igraph Creo que la conversión a data.frame está devolviendo un data frame con una sola columna llamada

Hi, I am currently working on a more or less intrusive patch (D37896), which pulls optimizations on multiplications from some back-ends, e.g., (mul x, 2^N + 1) => (add (shl x, N), x) in AArch64, into the DAGCombiner to have this optimization generic on all targets. However, running the LLVM Tests leads to 67 unexpected results. Am 19.09.2017 um 15:58 schrieb Sanjay Patel: > For the

Good evening, Yuan Excuse me, I gave up Debug build earlier due to my poor hosts. I will improve able to build Debug ;) You may build with --enable-optimized=yes (or, make ENABLE_OPTIMIZED=1) btw, DLL builder has implemented since Aug. It might be easier to port DLL stuff to 2.6 :) Do you try? ...Takumi 2010年9月2日 17:16:25 UTC+9 yuan zheng <tsinghuayuan86 at gmail.com>: > Hello,

There are multiple problems/questions here: 1. Make sure you've updated trunk to the latest rev before running update_llc_test_checks.py on lea-3.ll. Ie, I would only expect the output you're seeing if you're running the script on a version of that test file before r313631. After that commit, each RUN has its own check prefix, so there should be no conflict opportunity. 2. I

Hi Sanjay, thanks for this information. I did get a little bit further with the patch. However, Hexagon gives me headaches. I tried to limit the scope of the patch to the BeforeLegalizeTypes phase and Hexagon still reaches the unreachable. Hexagon tries to split or widen a vector type for a node with custom lowering where the unreachable arises from inside TargetLowering::ReplaceNodeResults

Is VT a legal type on Hexagon? It looks like Hexagon may be setting SHL as Custom for every defined vector type. Try adding TLI.isTypeLegal(VT) too. ~Craig On Thu, Sep 21, 2017 at 10:06 PM, Haidl, Michael < michael.haidl at uni-muenster.de> wrote: > Hi Sanjay, > > thanks for this information. I did get a little bit further with the > patch. However, Hexagon gives me headaches.

I use Sony (previously Sonic Foundry) Sound Forge, which allows me to save audio files in .w64 (Wave 64) format to get around the 2GB .wav file limitation. W64 was invented by Sonic Foundry, and is an open format as far as I know. The only programs I know about using the .w64 format at the moment are Sound Forge and Steinberg Nuendo, although there may be others out there. With increasing

Hi, I've been hacking around something missing in the assemble for the mingw-w64 targets the tfloat variable. I did some research into the llvm sources and did see x86_fp80 which seems to be the same thing. Can we support the .tfloat variable or the alternative ? Or is it under another name? I've tried using .x86_fp80 instead but to no avail. :/ Here is how tfloat is being used in