はてなブックマーク

Our releases are available on the GNU FTP server and its mirrors. The following sites mirror the gcc.gnu.org download site (Phoenix, Arizona, USA) directly: France (no snapshots): ftp.lip6.fr, thanks to ftpmaint@lip6.fr France, Brittany: ftp.irisa.fr, thanks to ftpmaint@irisa.fr Germany, Berlin: ftp.fu-berlin.de, thanks to ftp@fu-berlin.de Germany: ftp.gwdg.de, thanks to ftp@gwdg.de Germany: mpi-s

6.52 Getting the Return or Frame Address of a Function ¶ These functions may be used to get information about the callers of a function. Built-in Function: void * __builtin_return_address (unsigned int level) ¶ This function returns the return address of the current function, or of one of its callers. The level argument is number of frames to scan up the call stack. A value of 0 yields the return

The libstdc++ parallel mode is an experimental parallel implementation of many algorithms of the C++ Standard Library. Several of the standard algorithms, for instance std::sort, are made parallel using OpenMP annotations. These parallel mode constructs can be invoked by explicit source declaration or by compiling existing sources with a specific compiler flag. Note The parallel mode has not been

Graphite: Gimple Represented as Polyhedra Graphite is a framework for high-level memory optimizations using the polyhedral model. The Graphite branch has been merged in August 2008 into trunk. Architecture of Graphite Graphite-4.8 also see plans at http://gcc.gnu.org/ml/gcc/2012-02/msg00186.html. For the branch merge into the GCC 4.8 trunk, see also http://gcc.gnu.org/ml/gcc-patches/2012-06/msg014

Split Stacks in GCC Ian Lance Taylor The goal of split stacks is to permit a discontiguous stack which is grown automatically as needed. This means that you can run multiple threads, each starting with a small stack, and have the stack grow and shrink as required by the program. It is then no longer necessary to think about stack requirements when writing a multi-threaded program. The memory usage

GCC provides experimental support for the upcoming ISO C++ standard, C++0x. This support can be enabled with the -std=c++0x or -std=gnu++0x compiler options; the former disables GNU extensions. GCC's C++0x mode tracks the C++0x working paper drafts produced by the ISO C++ committee, available on the ISO C++ committee's web site at https://www.open-std.org/jtc1/sc22/wg21/. Since this standard is st

This FAQ tries to answer specific questions concerning GCC. For general information regarding C, C++, and Fortran respectively, please check the comp.lang.c FAQ and the C++ FAQ. Other GCC-related FAQs: libstdc++-v3. General information How do I get a bug fixed or a feature added? Does GCC work on my platform? Installation How to install multiple versions of GCC Dynamic linker is unable to find GCC

GCC 4.3 Release Series Porting to the New Tools The GCC 4.3 release series differs from previous GCC releases in more than the usual list of new features. Some of these changes are a result of bug fixing, and some old behaviors have been intentionally changed in order to support new standards, or relaxed in standards-conforming ways to facilitate compilation or runtime performance. Some of these c

Prerequisites for GCC GCC requires that various tools and packages be available for use in the build procedure. Modifying GCC sources requires additional tools described below. Tools/packages necessary for building GCC ISO C++11 compiler Necessary to bootstrap GCC. GCC 4.8.3 or newer has sufficient support for used C++11 features, with earlier GCC versions you might run into implementation bugs. V

6 Extensions to the C Language Family ¶ GNU C provides several language features not found in ISO standard C. (The -pedantic option directs GCC to print a warning message if any of these features is used.) To test for the availability of these features in conditional compilation, check for a predefined macro __GNUC__, which is always defined under GCC. These extensions are available in C and Objec

GCC 4.4 Release Series Changes, New Features, and Fixes The latest release in the 4.4 release series is GCC 4.4.7. Caveats __builtin_stdarg_start has been completely removed from GCC. Support for <varargs.h> had been deprecated since GCC 4.0. Use __builtin_va_start as a replacement. Some of the errors issued by the C++ front end that could be downgraded to warnings in previous releases by using -f

10 gcov—a Test Coverage Program ¶ gcov is a tool you can use in conjunction with GCC to test code coverage in your programs. Introduction to gcov Invoking gcov Using gcov with GCC Optimization Brief Description of gcov Data Files Data File Relocation to Support Cross-Profiling Profiling and Test Coverage in Freestanding Environments

This page has been incorporated into another. If you are not redirected automatically, click here. For questions related to the use of GCC, please consult these web pages and the GCC manuals. If that fails, the gcc-help@gcc.gnu.org mailing list might help. Comments on these web pages and the development of GCC are welcome on our developer list at gcc@gcc.gnu.org. All of our lists have public archi

This file documents the use of the GNU compilers. Copyright © 1988-2024 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with the Invariant Sections being “Funding Free Software”, the Front-Cover Texts being (a) (see

4. Extensions to the C Language Family GNU C provides several language features not found in ANSI standard C. (The `-pedantic' option directs GNU CC to print a warning message if any of these features is used.) To test for the availability of these features in conditional compilation, check for a predefined macro __GNUC__, which is always defined under GNU CC. These extensions are available in C a

The C preprocessor implements the macro language used to transform C, C++, and Objective-C programs before they are compiled. It can also be useful on its own. Copyright © 1987-2024 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Softwar

The GOMP project consists of implementation of OpenMP and OpenACC to permit annotating the source code to permit running it concurrently with thread parallelization and on offloading devices (accelerators such as GPUs), including the associated run-time library and API routines. Both OpenMP and OpenACC are supported with GCC's C, C++ and Fortran compilers. Content Usage Documentation History and P

GCC 4.2 Release Series Changes, New Features, and Fixes Caveats GCC no longer accepts the -fshared-data option. This option has had no effect in any GCC 4 release; the targets to which the option used to apply had been removed before GCC 4.0. General Optimizer Improvements New command-line options specify the possible relationships among parameters and between parameters and global data. For examp

Installing GCC: Configuration Like most GNU software, GCC must be configured before it can be built. This document describes the recommended configuration procedure for both native and cross targets. We use srcdir to refer to the toplevel source directory for GCC; we use objdir to refer to the toplevel build/object directory. If you obtained the sources by cloning the repository, srcdir must refer

The mudflap run time checker was removed in GCC 4.9 and it is superseded by Address Sanitizer. The mudflap options remain, but do nothing. This page applies only to earlier versions of GCC. Mudflap Pointer Debugging It is enabled by passing -fmudflap to the compiler. For front-ends that support it (C and very simple C++ programs), it instruments all risky pointer/array dereferencing operations, so

Table of Contents Reporting Bugs What we need What we DON'T want Where to post it Detailed bug reporting instructions Detailed bug reporting instructions for GNAT Detailed bug reporting instructions when using a precompiled header Frequently Reported Bugs Non-bugs General C C++ Common problems when upgrading the compiler Reporting Bugs A good bug report, which is complete and self-contained, enabl

5.44 Built-in functions for atomic memory access The following builtins are intended to be compatible with those described in the Intel Itanium Processor-specific Application Binary Interface, section 7.4. As such, they depart from the normal GCC practice of using the “__builtin_” prefix, and further that they are overloaded such that they work on multiple types. The definition given in the Intel

Binaries available for gfortran This page gathers links to all unofficial gfortran binary packages people regularly build, based on the current development gfortran source code. Windows MacOS GNU/Linux Build GNU Fortran from source Note: There do not exist any official FSF/GNU/GCC binary builds (only source packages). Most of the builds below come from gfortran maintainers but not all. Windows If

This file documents the internals of the GNU compilers. Copyright © 1988-2024 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with the Invariant Sections being “Funding Free Software”, the Front-Cover Texts being (a)