mingw-w64

Installing MinGW-w64 5.1 I find -fsanitize=address is available. It compiles fine, and when it starts linking I get thousands of: undefined reference to '__asan_report_load1' undefined reference to '__asan_report_load4' I googled and found libasan referenced various places, but also comments that when you include -fsanitize=address it automatically includes that library for linking. I searched the MinGW-w64 5.1 install dirctory for "asan" and it was not found anywhere. What do I need to add on to use address sanitizing features in MinGW-w64? Thank you. I've looked quickly into release notes

I am using Ubuntu 13.04 and installed mingw-w64 using apt-get install mingw-w64 . I can compile and link a working 64-bit version of my program with the following command: x86_64-w64-mingw32-g++ code.cpp -o app.exe Which generates a 64-bit app.exe file. What binary or command line flags do I use to generate a 32-bit version of app.exe? Alexander Shukaev That depends on which variant of toolchain you're currently using. Both DWARF and SEH variants (which come starting from GCC 4.8.0) are only single-target. You can see it yourself by inspecting the directory structure of their distributions, i

I had to format my laptop, and so I had to install Git again. However it is quite different from the one I had yesterday, the icon is not the default orange one anymore, it looks more like Chrome now. The bash is quite different, including a purple " MINGW64 " in every line. Why is it there? Is this the new final version? Or did I download something different? I downloaded https://github.com/git-for-windows/git/releases/download/v2.5.1.windows.1/Git-2.5.1-64-bit.exe from https://git-scm.com/downloads . Thanks! This is the new icon being used with Git for Windows 2.x . The website needs an

opencv installation using mingw32-make command in windows 10 platform, then likely end up in getting the below error. Windows version : 10 OpenCv:3.2.0 Please suggest me in installing. D:\installers\opencv\sources\modules\ts\src\ts_gtest.cpp: In constructor 'testing::internal::Mutex::Mutex()': D:\installers\opencv\sources\modules\ts\src\ts_gtest.cpp:8829:45: error: cannot convert 'CRITICAL_SECTION* {aka _CRITICAL_SECTION*}' to '_RTL_CRITICAL_SECTION*' in initialization critical_section_(new CRITICAL_SECTION) { ^ D:\installers\opencv\sources\modules\ts\src\ts_gtest.cpp:8830:48: error: cannot

I have a union that looks like this union bareVec8f { __m256 m256; //avx 8x float vector float floats[8]; int ints[8]; inline bareVec8f(){ } inline bareVec8f(__m256 vec){ this->m256 = vec; } inline bareVec8f &operator=(__m256 m256) { this->m256 = m256; return *this; } inline operator __m256 &() { return m256; } } the __m256 needs to be aligned on 32 byte boundary to be used with SSE functions, and should be automatically, even within the union. And when I do this bareVec8f test = _mm256_set1_ps(1.0f); I get a segmentation fault. This code should work because of the constructor I made. However,

Consider the following C program: #include <stdio.h> #include <stdarg.h> typedef void (callptr)(); static void fixed(void *something, double val) { printf("%f\n", val); } static void dynamic(void *something, ...) { va_list args; va_start(args, something); double arg = va_arg(args, double); printf("%f\n", arg); } int main() { double x = 1337.1337; callptr *dynamic_func = (callptr *) &dynamic; dynamic_func(NULL, x); callptr *fixed_func = (callptr *) &fixed; fixed_func(NULL, x); printf("%f\n", x); } Basically, the idea is to store a function with variable arguments in a "generic" function pointer

Are there any OpenMP binaries out there for the MinGW-w64 GCC compiler (Windows)? There is TDM-GCC (Windows) and sezero's Personal Build (Linux and Windows). update 2012/11: Distribution Host OS MinGW-w64 Cygwin, Darwin, Linux and Windows TDM-GCC Windows MinGW-builds Windows 来源： https://stackoverflow.com/questions/5532826/openmp-for-mingw-w64

When I try to compile a 32-bit program on a 64-bit host with MinGW-builds : T:\mingw64>.\bin\g++ -m32 Test.cpp I get: t:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.0/../../../../x86_64-w64-mingw32/bin/ld.exe: skipping incompatible t:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.0/libstdc++.dll.a when searching for -lstdc++ t:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.0/../../../../x86_64-w64-mingw32/bin/ld.exe: skipping incompatible t:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.0/libstdc++.a when searching for -lstdc++ t:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.0/../../../..

What's the difference between the MinGW project and the 32-bit portion of the MinGW-w64 project? Does the 32-bit portion of MinGW-w64 have any relation to x64 at all? It seems like their compilers do the exact same things... One looks like it "cross compiles", from 64 bit to 32 bit, whereas the other looks native. That was just a quick look though, so I could be a long long way off the mark here...... EDIT: This is only somewhat true. A better explanation is provided here The MinGW from http://www.mingw.org/ does only support gcc 32 bit (host and target). The independent minGW-w64 project