サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
災害への備え
gcc.gnu.org
Date: July 12 to 14, 2013. Location: Google Headquarters Building 1200, 1200 Charleston Rd, Mountain View, California, USA http://goo.gl/maps/y4Kei Registration Fee: No charge. This event is completely funded by Google. WE HAVE REACHED CAPACITY. We cannot accept any more registrations. Sorry. Submission deadline: 28 February 2013. Note: we will also accept "last minute" BoF/talks at the conference
6.35 Declaring Attributes of Functions ¶ In GNU C and C++, you can use function attributes to specify certain function properties that may help the compiler optimize calls or check code more carefully for correctness. For example, you can use attributes to specify that a function never returns (noreturn), returns a value depending only on the values of its arguments (const), or has printf-style ar
GCC 4.9 Release Series Changes, New Features, and Fixes Caveats The mudflap run time checker has been removed. The mudflap options remain, but do nothing. Support for a number of older systems and recently unmaintained or untested target ports of GCC has been declared obsolete in GCC 4.9. Unless there is activity to revive them, the next release of GCC will have their sources permanently removed.
GCC 4.8 Release Series Changes, New Features, and Fixes Caveats GCC now uses C++ as its implementation language. This means that to build GCC from sources, you will need a C++ compiler that understands C++ 2003. For more details on the rationale and specific changes, please refer to the C++ conversion page. To enable the Graphite framework for loop optimizations you now need CLooG version 0.18.0 a
The GCC 4.7 release series differs from previous GCC releases in more than the usual list of changes. Some of these 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 changes are not visible to the naked eye and will not cause pr
Merge from cxx-conversion branch (http://gcc.gnu.org/wiki/cxx-conversion). As described in http://gcc.gnu.org/ml/gcc/2012-08/msg00015.html, this patch changes the default bootstrap process so that stage 1 always builds with a C++ compiler. Other than the bootstrap change, the patch makes no functional changes to the compiler. Everything should build as it does now in trunk. The main changes in t
Our bug reporting instructions ask that a bug report include the preprocessed version of the file that triggers the bug. There are several methods to minimise a testcase. This page ought to serve as an introduction to automatic testcase reduction using C-Vise tools or C-Reduce tools. Simple ICE reduction We'll start with the most simple case, reducing the testcase for an internal compiler error (I
C++ Conversion This project is a continuation of the build GCC in C++ project. Its goal is to explore re-implementing some existing GCC components in C++. Related Projects Unified debugging dumps. Alternatives to GC. Simplified GIMPLE generation. Documentation New API for vectors. Status 2012-08-14: The branch has been merged into trunk. There is no code left in the branch for now. If major re-wri
(This release series is no longer supported.) June 12, 2014 The GNU project and the GCC developers are pleased to announce the release of GCC 4.7.4. This release is a bug-fix release, containing fixes for regressions in GCC 4.7.3 relative to previous releases of GCC. Release History GCC 4.7.4 June 12, 2014 (changes, documentation) GCC 4.7.3 April 11, 2013 (changes, documentation) GCC 4.7.2 Septemb
From: Jakub Jelinek <jakub at redhat dot com> To: gcc-announce at gcc dot gnu dot org, gcc at gcc dot gnu dot org Date: Thu, 1 Mar 2012 16:26:08 +0100 Subject: GCC 4.6.3 Released Reply-to: Jakub Jelinek <jakub at redhat dot com> The GNU Compiler Collection version 4.6.3 has been released. GCC 4.6.3 is a bug-fix release containing fixes for regressions and serious bugs in GCC 4.6.2, with over 70 bu
A simple program gives incorrect floating point results when compiled with the -O flag. The complete source code is in the How-To-Repeat section below. This program prints "error" when compiled with -O; clearly wrong. The unoptimized code correctly prints no output. Also, if I try to print out the value of y2 before the comparison with y, then the correct value is output, and there is no "error" m
Transactional Memory in GCC Background Transactional memory is intended to make programming with threads simpler, in particular synchronizing access to data shared between several threads using transactions. As with databases, a transaction is a unit of work that either completes in its entirety or has no effect at all (i.e., transactions execute atomically). Further, transactions are isolated fro
24 Plugins ¶ GCC plugins are loadable modules that provide extra features to the compiler. Like GCC itself they can be distributed in source and binary forms. GCC plugins provide developers with a rich subset of the GCC API to allow them to extend GCC as they see fit. Whether it is writing an additional optimization pass, transforming code, or analyzing information, plugins can be quite useful. Lo
3.11 Options That Control Optimization ¶ These options control various sorts of optimizations. Without any optimization option, the compiler’s goal is to reduce the cost of compilation and to make debugging produce the expected results. Statements are independent: if you stop the program with a breakpoint between statements, you can then assign a new value to any variable or change the program cou
This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project. From: Linus Torvalds <torvalds at transmeta dot com> To: kevin at atkinson dot dhs dot org, gcc at gcc dot gnu dot org Cc: Date: Fri, 9 Aug 2002 20:28:16 -0700 Subject: Re: Faster compilation speed Newsgroups: linux.egcs Organization: References: <200208100156.g7A1uwn01415@penguin.transmeta.com> In article <Pine.LNX.
GCC 4.7 Release Series Changes, New Features, and Fixes Caveats The -fconserve-space flag has been deprecated. The flag had no effect for most targets: only targets without a global .bss section and without support for switchable sections. Furthermore, the flag only had an effect for G++, where it could result in wrong semantics (please refer to the GCC manual for further details). The flag will b
Full support for C/C++ atomic operations as specified in draft ISO C and C++ documents. The C++11 Memory Model and GCC: Summarized information and the GCC implementation details. For C, see "Parallel memory sequencing model proposal" N1349 For C++, see "The C++ memory model" and the "Atomic operations library" chapter in the most recent draft: N3290: Final draft standard as of 11-Apr-2011 A Less F
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
From: Ian Lance Taylor <iant at google dot com> To: gcc at gcc dot gnu dot org Date: Sat, 23 Oct 2010 22:40:46 -0700 Subject: Discussion about merging Go frontend The Go frontend was approved for inclusion with gcc by the steering committee a while back: http://gcc.gnu.org/ml/gcc/2010-01/msg00500.html . Assuming it is OK with the release managers, I would like to get it into the gcc 4.6 release. I
Short Contents Copyright (C) 2008-2024 FSF Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. This is the top level of the libstdc++ documentation set. The documenta
Background Compiler plugins (or loadable modules) make it possible for a developer to add new features to the compiler without having to modify the compiler itself. Plugin support is available in GCC version 4.5.0 and later. Plugin functionality provides several advantages: It shortens the time needed to build and test new features. Only the code needed to implement the new functionality needs to
6.63 Other Built-in Functions Provided by GCC ¶ GCC provides a large number of built-in functions other than the ones mentioned above. Some of these are for internal use in the processing of exceptions or variable-length argument lists and are not documented here because they may change from time to time; we do not recommend general use of these functions. The remaining functions are provided for
GCC 4.6 Release Series Changes, New Features, and Fixes Caveats The options -b <machine> and -V <version> have been removed because they were unreliable. Instead, users should directly run <machine>-gcc when cross-compiling, or <machine>-gcc-<version> to run a different version of gcc. GCC now has stricter checks for invalid command-line options. In particular, when gcc was called to link object f
(This release series is no longer supported.) Jul 2, 2012 The GNU project and the GCC developers are pleased to announce the release of GCC 4.5.4. This release is a bug-fix release, containing fixes for regressions in GCC 4.5.3 relative to previous releases of GCC. Release History GCC 4.5.4 Jul 2, 2012 (changes) GCC 4.5.3 Apr 28, 2011 (changes) GCC 4.5.2 Dec 16, 2010 (changes) GCC 4.5.1 Jul 31, 20
C++ applications often depend on specific language support routines, say for throwing exceptions, or catching exceptions, and perhaps also depend on features in the C++ Standard Library. The C++ Standard Library has many include files, types defined in those include files, specific named functions, and other behavior. The text of these behaviors, as written in source include files, is called the A
3.19.5 ARM Options ¶ These ‘-m’ options are defined for the ARM port: -mabi=name ¶ Generate code for the specified ABI. Permissible values are: ‘apcs-gnu’, ‘atpcs’, ‘aapcs’, ‘aapcs-linux’ and ‘iwmmxt’. -mapcs-frame ¶ Generate a stack frame that is compliant with the ARM Procedure Call Standard for all functions, even if this is not strictly necessary for correct execution of the code. Specifying -
6.53 Function Names as Strings ¶ GCC provides three magic constants that hold the name of the current function as a string. In C++11 and later modes, all three are treated as constant expressions and can be used in constexpr constexts. The first of these constants is __func__, which is part of the C99 standard: The identifier __func__ is implicitly declared by the translator as if, immediately fol
Status The branch has been merged to trunk and is now closed. Final merge announcement: http://gcc.gnu.org/ml/gcc/2009-10/msg00060.html Background Link Time Optimization (LTO) gives GCC the capability of dumping its internal representation (GIMPLE) to disk, so that all the different compilation units that make up a single executable can be optimized as a single module. This expands the scope of in
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
次のページ
このページを最初にブックマークしてみませんか?
『GCC, the GNU Compiler Collection - GNU Project』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く