/external/llvm/test/CodeGen/X86/ |
D | segmented-stacks.ll | 7 …%s -mcpu=generic -mtriple=i686-mingw32 -verify-machineinstrs | FileCheck %s -check-prefix=X32-MinGW 11 … -mcpu=generic -mtriple=x86_64-mingw32 -verify-machineinstrs | FileCheck %s -check-prefix=X64-MinGW 102 ; X32-MinGW-LABEL: test_basic: 104 ; X32-MinGW: cmpl %fs:20, %esp 105 ; X32-MinGW-NEXT: ja LBB0_2 107 ; X32-MinGW: pushl $0 108 ; X32-MinGW-NEXT: pushl $48 109 ; X32-MinGW-NEXT: calll ___morestack 110 ; X32-MinGW-NEXT: ret 112 ; X64-MinGW-LABEL: test_basic: [all …]
|
/external/clang/lib/Driver/ |
D | MinGWToolChain.cpp | 45 void MinGW::findGccLibDir() { in findGccLibDir() 65 MinGW::MinGW(const Driver &D, const llvm::Triple &Triple, const ArgList &Args) in MinGW() function in MinGW 93 bool MinGW::IsIntegratedAssemblerDefault() const { return true; } in IsIntegratedAssemblerDefault() 95 Tool *MinGW::getTool(Action::ActionClass AC) const { in getTool() 110 Tool *MinGW::buildAssembler() const { in buildAssembler() 111 return new tools::MinGW::Assembler(*this); in buildAssembler() 114 Tool *MinGW::buildLinker() const { return new tools::MinGW::Linker(*this); } in buildLinker() 116 bool MinGW::IsUnwindTablesDefault() const { in IsUnwindTablesDefault() 120 bool MinGW::isPICDefault() const { return getArch() == llvm::Triple::x86_64; } in isPICDefault() 122 bool MinGW::isPIEDefault() const { return false; } in isPIEDefault() [all …]
|
/external/opencv3/3rdparty/ffmpeg/ |
D | build_win32.txt | 2 Right now it assumes that 32-bit MinGW is in the system path and 13 1. Install 32-bit MinGW + MSYS from 14 http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/ 16 2. Install 64-bit MinGW. http://mingw-w64.sourceforge.net/
|
/external/pcre/dist/doc/html/ |
D | NON-AUTOTOOLS-BUILD.txt | 307 paradigm on Windows systems: using MinGW or using Cygwin. These are not at all 312 The MinGW home page (http://www.mingw.org/) says this: 314 MinGW: A collection of freely available and freely distributable Windows 331 On both MinGW and Cygwin, PCRE should build correctly using: 357 MinGW has no such restrictions. The MinGW compiler generates a library or 364 to tell Cygwin's gcc to use the MinGW gcc. Cygwin's gcc is only acting as a 365 front end to MinGW's gcc (if you install Cygwin's gcc, you get both Cygwin's 366 gcc and MinGW's gcc). So, a user can: 368 . Build native binaries by using MinGW or by getting Cygwin and using 385 Borland, Msys, MinGW, NMake, and Unix. If possible, use short paths with no [all …]
|
/external/pcre/dist/ |
D | NON-AUTOTOOLS-BUILD | 307 paradigm on Windows systems: using MinGW or using Cygwin. These are not at all 312 The MinGW home page (http://www.mingw.org/) says this: 314 MinGW: A collection of freely available and freely distributable Windows 331 On both MinGW and Cygwin, PCRE should build correctly using: 357 MinGW has no such restrictions. The MinGW compiler generates a library or 364 to tell Cygwin's gcc to use the MinGW gcc. Cygwin's gcc is only acting as a 365 front end to MinGW's gcc (if you install Cygwin's gcc, you get both Cygwin's 366 gcc and MinGW's gcc). So, a user can: 368 . Build native binaries by using MinGW or by getting Cygwin and using 385 Borland, Msys, MinGW, NMake, and Unix. If possible, use short paths with no [all …]
|
/external/deqp/framework/delibs/cmake/ |
D | toolchain-mingw-clang.cmake | 8 set(MINGW_BASE "C:/mingw" CACHE STRING "MinGW base directory")
|
/external/gptfdisk/ |
D | README.Windows | 106 - MinGW (http://www.mingw.org), and in particular its Linux-hosted 108 Makefile.mingw64 files enable compilation of the software via MinGW. 111 using another compiler or even using MinGW under Windows or another Linux 125 The MinGW compiler produces much larger executables than do the MS
|
/external/libmtp/ |
D | README.windows.txt | 9 … using MingW/MSys. The source relies upon the __WIN32__ macro which is defined by MinGW by default. 19 With both of these libraries extracted and placed in MinGW's search path, you can compile the libra…
|
/external/llvm/lib/Support/Windows/ |
D | Signals.inc | 37 // The version of g++ that comes with MinGW does *not* properly understand 38 // the ll format specifier for printf. However, MinGW passes the format 42 // we will turn off the warnings for this just file. However, MinGW also does 49 // MinGW.org does not have updated support for the 64-bit versions of the 467 // The following functions are not reliably accessible on MinGW. 617 // We turned these warnings off for this file so that MinGW-g++ doesn't 619 // warnings back on. If MinGW starts to support diagnostic stacks, we can
|
/external/icu/icu4c/source/ |
D | runConfigureICU | 53 MinGW Use the GNU gcc/g++ compilers on MinGW 311 MinGW)
|
/external/mesa3d/src/gallium/targets/libgl-gdi/ |
D | SConscript | 31 # DEF parser in certain versions of MinGW is busted, as does not behave as
|
/external/dbus/ |
D | README.cmake | 13 Win32 MinGW-w64|32 21 cmake -G "MinGW Makefiles" [<options, see below>] <dbus-src-root>/cmake
|
/external/icu/icu4c/source/config/ |
D | mh-mingw | 2 ## Cygwin/MinGW specific setup 157 ## End Cygwin/MinGW specific setup
|
/external/libjpeg-turbo/ |
D | BUILDING.txt | 311 MinGW Build on Cygwin 475 ** Building on Windows (Visual C++ or MinGW) 509 -- MinGW 511 MinGW-builds (http://sourceforge.net/projects/mingwbuilds/) or 611 MinGW 618 cmake -G "MinGW Makefiles" {source_directory} 722 64-bit MinGW Build on Cygwin 737 32-bit MinGW Build on Cygwin 752 MinGW Build on Linux 846 If using MinGW:
|
/external/wpa_supplicant_8/wpa_supplicant/ |
D | README-Windows.txt | 36 The default build setup for wpa_supplicant is to use MinGW and 37 cross-compiling from Linux to MinGW/Windows. It should also be 38 possible to build this under Windows using the MinGW tools, but that 114 with the open source version of Qt4 and MinGW. Following commands can
|
/external/tlsdate/m4/ |
D | ax_platform.m4 | 52 AC_DEFINE([TARGET_OS_MINGW],[1],[Whether we build for MinGW])],
|
/external/libxml2/bakefile/ |
D | Readme.txt | 12 - makefile.gcc for MinGW MINGW32-MAKE
|
/external/eigen/doc/ |
D | WrongStackAlignment.dox | 8 This is an issue that, so far, we met only with GCC on Windows: for instance, MinGW and TDM-GCC.
|
D | UnalignedArrayAssert.dox | 77 This is a must-read for people using GCC on Windows (like MinGW or TDM-GCC). If you have this asser…
|
/external/harfbuzz_ng/win32/ |
D | info-msvc.mak | 122 @echo MinGW builds.
|
/external/libvpx/libvpx/ |
D | README | 18 many *nix platforms, as well as MinGW and Cygwin. If coreutils is not
|
/external/libogg/ |
D | README | 90 It is also possible to cross compile from Linux to windows using the MinGW
|
/external/llvm/cmake/modules/ |
D | HandleLLVMOptions.cmake | 182 # On Windows all code is PIC. MinGW warns if -fPIC is used. 189 # MinGW warns if -fvisibility-inlines-hidden is used. 434 # MinGW and Cygwin are a bit stricter and lack things like
|
/external/zlib/src/ |
D | CMakeLists.txt | 171 # This gets us DLL resource information when compiling on MinGW.
|
/external/google-breakpad/src/testing/gtest/ |
D | CHANGES | 26 * Compatibility fixes for Android, Google Native Client, MinGW, HP UX,
|