• Home
  • Raw
  • Download

Lines Matching refs:GCC

121 |AuroraUX         | x86\ :sup:`1`        | GCC                     |
123 |Linux | x86\ :sup:`1` | GCC |
125 |Linux | amd64 | GCC |
127 |Linux | ARM\ :sup:`13` | GCC |
129 |Solaris | V9 (Ultrasparc) | GCC |
131 |FreeBSD | x86\ :sup:`1` | GCC |
133 |FreeBSD | amd64 | GCC |
135 |MacOS X\ :sup:`2`| PowerPC | GCC |
137 |MacOS X\ :sup:`9`| x86 | GCC |
139 |Cygwin/Win32 | x86\ :sup:`1, 8, 11` | GCC 3.4.X, binutils 2.20|
149 | AIX\ :sup:`3,4` | PowerPC | GCC |
151 | Linux\ :sup:`3,5` | PowerPC | GCC |
153 | Linux\ :sup:`7` | Alpha | GCC |
155 | Linux\ :sup:`7` | Itanium (IA-64) | GCC |
159 | Windows x64 | x86-64 | mingw-w64's GCC-4.5.x\ :sup:`12` |
168 #. The GCC-based C/C++ frontend does not build
214 | `GCC <http://gcc.gnu.org/>`_ | 3.4.2 | C/C++ compiler\ …
278 Broken versions of GCC and other tools
282 bugs in the compiler. In particular, several versions of GCC crash when trying
283 to compile LLVM. We routinely use GCC 4.2 (and higher) or Clang. Other
284 versions of GCC will probably work as well. GCC versions listed here are known
286 GCC to something more recent. If you run into a problem with a version of GCC
288 the "``gcc -v``" command to find out which version of GCC you are using.
290 **GCC versions prior to 3.0**: GCC 2.96.x and before had several problems in the
293 **GCC 3.2.2 and 3.2.3**: These versions of GCC fails to compile LLVM with a
296 **GCC 3.3.2**: This version of GCC suffered from a `serious bug
298 "``convert_from_eh_region_ranges_1``" GCC function.
300 **Cygwin GCC 3.3.3**: The version of GCC 3.3.3 commonly shipped with Cygwin does
303 **SuSE GCC 3.3.3**: The version of GCC 3.3.3 shipped with SuSE 9.1 (and possibly
306 version of GCC.
308 **GCC 3.4.0 on linux/x86 (32-bit)**: GCC miscompiles portions of the code
312 **GCC 3.4.2 on linux/x86 (32-bit)**: GCC miscompiles portions of the code
317 **GCC 3.4.x on X86-64/amd64**: GCC `miscompiles portions of LLVM
320 **GCC 3.4.4 (CodeSourcery ARM 2005q3-2)**: this compiler miscompiles LLVM when
324 **IA-64 GCC 4.0.0**: The IA-64 version of GCC 4.0.0 is known to miscompile LLVM.
326 **Apple Xcode 2.3**: GCC crashes when compiling LLVM at -O3 (which is the
330 **GCC 4.1.1**: GCC fails to build LLVM with template concept check errors
331 compiling some files. At the time of this writing, GCC mainline (4.2) did not
334 **GCC 4.1.1 on X86-64/amd64**: GCC `miscompiles portions of LLVM
339 **GCC 4.1.2 on OpenSUSE**: Seg faults during libstdc++ build and on x86_64
342 **GCC 4.1.2 (20061115 (prerelease) (Debian 4.1.1-21)) on Debian**: Appears to
346 **GCC 4.1.2 20071124 (Red Hat 4.1.2-42)**: Suffers from the same symptoms as the
349 **Cygwin GCC 4.3.2 20080827 (beta) 2**: Users `reported
351 this GCC version.
353 **Debian GCC 4.3.2 on X86**: Crashes building some files in LLVM 2.6.
355 **GCC 4.3.3 (Debian 4.3.3-10) on ARM**: Miscompiles parts of LLVM 2.6 when
359 **SUSE 11 GCC 4.3.4**: Miscompiles LLVM, causing crashes in ValueHandle logic.
361 **GCC 4.3.5 and GCC 4.4.5 on ARM**: These can miscompile ``value >> 1`` even at
365 **GCC 4.6.3 on ARM**: Miscompiles ``llvm-readobj`` at ``-O3``. A test failure
387 recommend using the system GCC to compile LLVM and Clang in this case.
444 and the LLVM GCC front end compiled for your platform. There is an additional
714 | | ``configure`` will check ``PATH`` for ``clang`` and GCC C |
720 | | ``clang++`` and GCC C++ compilers (in this order). Use |
729 Enables optimized compilation (debugging symbols are removed and GCC
805 with GCC optimizations enabled and strip debugging information from the
823 GCC that is known not to compile LLVM.
856 install bitcode libraries into the GCC front end's bitcode library directory.
931 GCC compiler supports.
1136 Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front end
1306 Clang works just like GCC by default. The standard -S and -c arguments